This is the mail archive of the gcc-patches@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]

Re: Patch for AMD Dispatch Scheduler


I have not seen any complaint yet. Theoretically it should select dispatch scheduling if "-march=bdver1 -mdispatch-scheduler -O3" flags are selected. Otherwis the behavior should be the same as before.

If you think the bug that you noticed is related to this change, please file a bug and let me know, and I will look at it.

Reza

--- On Tue, 9/14/10, Steve Ellcey <sje@cup.hp.com> wrote:

> From: Steve Ellcey <sje@cup.hp.com>
> Subject: Re: Patch for AMD Dispatch Scheduler
> To: "reza yazdani" <yazdani_reza@yahoo.com>, "Sebastian Pop" <sebpop@gmail.com>
> Cc: gcc-patches@gcc.gnu.org, "Vladimir Makarov" <vmakarov@redhat.com>, jh@suse.cz, "Richard Henderson" <rth@redhat.com>, "Uros Bizjak" <ubizjak@gmail.com>
> Date: Tuesday, September 14, 2010, 11:20 AM
> Reza or Sebastian,
> 
> Has anyone reported any problems with this patch?? I
> am getting a failure
> on ia64-hp-hpux11.23 with:
> 
> | build/genhooks \
> |? ? ?
> ???/proj/opensrc/nightly/src/trunk/gcc/doc/tm.texi.in
> > tmp-tm.texi
> | echo timestamp > gcc.pod
> | 
> | out of memory allocating 4294967292 bytes after a total
> of 3665070616 bytes
> | make[3]: *** [s-tm-texi] Error 1
> 
> I haven't tracked the exact problem down yet but it
> definitely starts with
> r164133.? It might be related to using the selective
> scheduler, although
> I don't get this failure on ia64-unknown-linux-gnu.
> 
> Steve Ellcey
> sje@cup.hp.com
> 




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