[Bug regression/39914] 96% performance regression in floating point code; part of the problem started 2009/03/12-13

2009-04-26 Thread ubizjak at gmail dot com
--- Comment #1 from ubizjak at gmail dot com 2009-04-26 18:43 --- There are a couple of possible candidates in this range: URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=144812 Log: 2009-03-12 Vladimir Makarov PR debug/39432 * ira-int.h (struct allocno): Fix c

[Bug regression/39914] 96% performance regression in floating point code; part of the problem started 2009/03/12-13

2009-04-27 Thread ubizjak at gmail dot com
--- Comment #2 from ubizjak at gmail dot com 2009-04-27 08:16 --- (In reply to comment #0) > (same .i file, same instructions for reproducing, same compiler options, same > everything) I guess that this is direct.i compiled with -O1? Trunk, revision: 146825 -O1 on x86_64 linux gives:

[Bug regression/39914] 96% performance regression in floating point code; part of the problem started 2009/03/12-13

2009-04-27 Thread lucier at math dot purdue dot edu
--- Comment #3 from lucier at math dot purdue dot edu 2009-04-27 15:07 --- Subject: Re: 96% performance regression in floating point code; part of the problem started 2009/03/12-13 On Sun, 2009-04-26 at 18:43 +, ubizjak at gmail dot com wrote: > > > --- Comment #1 from ubiz

[Bug regression/39914] 96% performance regression in floating point code; part of the problem started 2009/03/12-13

2009-04-27 Thread lucier at math dot purdue dot edu
--- Comment #4 from lucier at math dot purdue dot edu 2009-04-27 15:11 --- Subject: Re: 96% performance regression in floating point code; part of the problem started 2009/03/12-13 On Mon, 2009-04-27 at 08:16 +, ubizjak at gmail dot com wrote: > > > --- Comment #2 from ubiz

[Bug regression/39914] 96% performance regression in floating point code; part of the problem started 2009/03/12-13

2009-04-27 Thread pinskia at gcc dot gnu dot org
--- Comment #5 from pinskia at gcc dot gnu dot org 2009-04-27 15:26 --- This is by design -O1 is way slower than -O2 now. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added ---

[Bug regression/39914] 96% performance regression in floating point code; part of the problem started 2009/03/12-13

2009-04-27 Thread lucier at math dot purdue dot edu
--- Comment #6 from lucier at math dot purdue dot edu 2009-04-27 15:32 --- Subject: Re: 96% performance regression in floating point code; part of the problem started 2009/03/12-13 On Mon, 2009-04-27 at 15:26 +, pinskia at gcc dot gnu dot org wrote: > This is by design -O1 is wa

[Bug regression/39914] 96% performance regression in floating point code; part of the problem started 2009/03/12-13

2009-04-27 Thread lucier at math dot purdue dot edu
--- Comment #7 from lucier at math dot purdue dot edu 2009-04-27 15:35 --- Subject: Re: 96% performance regression in floating point code; part of the problem started 2009/03/12-13 On Mon, 2009-04-27 at 15:32 +, lucier at math dot purdue dot edu wrote: > On Mon, 2009-04-27 at 1

[Bug regression/39914] 96% performance regression in floating point code; part of the problem started 2009/03/12-13

2009-04-27 Thread lucier at math dot purdue dot edu
--- Comment #8 from lucier at math dot purdue dot edu 2009-04-27 16:29 --- I hadn't noticed before that Andrew had marked it as "RESOLVED INVALID". I'm reopening it, as I believe that resolving it as INVALID should require a more general discussion than a one-line dismissal of the bug.

[Bug regression/39914] 96% performance regression in floating point code; part of the problem started 2009/03/12-13

2009-04-27 Thread ubizjak at gmail dot com
--- Comment #9 from ubizjak at gmail dot com 2009-04-27 18:21 --- Following patch should fix the performance hit with -O1: --cut here-- Index: ira-conflicts.c === --- ira-conflicts.c (revision 146825) +++ ira-conflicts.