GNU bug report logs -
#6365
bidi data structure inefficiencies
Previous Next
Reported by: Dan Nicolaescu <dann <at> gnu.org>
Date: Mon, 7 Jun 2010 03:22:02 UTC
Severity: minor
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 6365 in the body.
You can then email your comments to 6365 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#6365
; Package
emacs
.
(Mon, 07 Jun 2010 03:22:02 GMT)
Full text and
rfc822 format available.
Message #3 received at submit <at> debbugs.gnu.org (full text, mbox):
Some bidi data structures are bigger that they need to be, this
probably results in additional cache misses.
Examples:
struct bidi_saved_info could use bitfields for the bidi_type_t members
Same for bidi_stack
bidi_it could use bitfields for a lot of it's members.
Information forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#6365
; Package
emacs
.
(Mon, 07 Jun 2010 13:38:02 GMT)
Full text and
rfc822 format available.
Message #6 received at 6365 <at> debbugs.gnu.org (full text, mbox):
> From: Dan Nicolaescu <dann <at> gnu.org>
> Date: Sun, 06 Jun 2010 23:21:32 -0400
> Cc:
>
> Some bidi data structures are bigger that they need to be, this
> probably results in additional cache misses.
> Examples:
>
> struct bidi_saved_info could use bitfields for the bidi_type_t members
> Same for bidi_stack
>
> bidi_it could use bitfields for a lot of it's members.
Thanks for the critical review and suggestions. I started a
discussion thread on emacs-devel about this, because I'm not sure
fixing this is a straight-forward matter. I will implement whatever
conclusions are reached there as part of solving this bug report.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6365
; Package
emacs
.
(Thu, 06 Oct 2011 20:53:01 GMT)
Full text and
rfc822 format available.
Message #9 received at 6365 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii wrote:
> Thanks for the critical review and suggestions. I started a
> discussion thread on emacs-devel about this, because I'm not sure
> fixing this is a straight-forward matter. I will implement whatever
> conclusions are reached there as part of solving this bug report.
Did anything happen with this?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6365
; Package
emacs
.
(Thu, 06 Oct 2011 21:09:02 GMT)
Full text and
rfc822 format available.
Message #12 received at 6365 <at> debbugs.gnu.org (full text, mbox):
> From: Glenn Morris <rgm <at> gnu.org>
> Cc: 6365 <at> debbugs.gnu.org
> Date: Thu, 06 Oct 2011 16:51:50 -0400
>
> Eli Zaretskii wrote:
>
> > Thanks for the critical review and suggestions. I started a
> > discussion thread on emacs-devel about this, because I'm not sure
> > fixing this is a straight-forward matter. I will implement whatever
> > conclusions are reached there as part of solving this bug report.
>
> Did anything happen with this?
See the discussion that started here:
https://lists.gnu.org/archive/html/emacs-devel/2010-06/msg00164.html
AFAIU, the conclusion was that there are no evident optimizations, and
that only profiling the current code against an alternative can tell
which one is better.
FWIW, I don't plan working o this any time soon.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6365
; Package
emacs
.
(Thu, 06 Oct 2011 21:14:02 GMT)
Full text and
rfc822 format available.
Message #15 received at 6365 <at> debbugs.gnu.org (full text, mbox):
> Date: Thu, 06 Oct 2011 23:04:54 +0200
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: 6365 <at> debbugs.gnu.org
>
> https://lists.gnu.org/archive/html/emacs-devel/2010-06/msg00164.html
>
> AFAIU, the conclusion was that there are no evident optimizations, and
> that only profiling the current code against an alternative can tell
> which one is better.
>
> FWIW, I don't plan working o this any time soon.
Oh, and I did convert 2 members of `struct bidi_it' from `int's to
1-bit fields.
Reply sent
to
Glenn Morris <rgm <at> gnu.org>
:
You have taken responsibility.
(Thu, 06 Oct 2011 21:23:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Dan Nicolaescu <dann <at> gnu.org>
:
bug acknowledged by developer.
(Thu, 06 Oct 2011 21:23:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 6365-done <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii wrote:
>> https://lists.gnu.org/archive/html/emacs-devel/2010-06/msg00164.html
>>
>> AFAIU, the conclusion was that there are no evident optimizations, and
>> that only profiling the current code against an alternative can tell
>> which one is better.
>>
>> FWIW, I don't plan working o this any time soon.
>
> Oh, and I did convert 2 members of `struct bidi_it' from `int's to
> 1-bit fields.
OK; doesn't seem worth keeping this open as a bug then.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 04 Nov 2011 11:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 13 years and 237 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.