This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/30961] [4.1/4.2 regression] redundant reg/mem stores/moves



------- Comment #18 from pluto at agmk dot net  2007-08-06 17:49 -------
(In reply to comment #17)
> (In reply to comment #16)
> > (In reply to comment #15)
> > > (In reply to comment #14)
> > > > (In reply to comment #13)
> > > > > Created an attachment (id=13550)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13550&action=view) [edit]
> > > > > An experimental patch
> > > > > 
> > > > > This patch works for the testcase.
> > > > 
> > > > i've applied this patch to 4.2.1 and compile testcases:
> > > > 
> > > > convert/m32/m64 look fine. load/m32/m64 still look unoptimal.
> > > > 
> > > 
> > > Gcc 4.3 works:
> > 
> > naturally but its not even been released yet.
> > users awaiting regression fixes for released compilers ;)
> > 
> 
> Load is fixed by dataflow merge.
> 

Dear H.J.Lu,
i'm not asking about 4.3 because it's far away future
and dataflow merge won't be a part of next 4.2 release.
i understand that developers love to play with unstable tree
instead of backporting fixes but we're awaiting regression
fixes for released compilers. after 4.3 release you'll jump
to 4.4 and leave 4.3 regressions in the same way as you
left 4.2 regressions. so, how we can motivate the gcc team
to fix regressions in non-trunk tree? do you expect donations?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30961


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]