On Sat, Apr 30, 2011 at 2:14 PM, Chris Demetriou c...@google.com wrote:
Makes -S output more easily preprocessable -- otherwise, the __i686 in
__i686.get_pc_think.reg chokes things.
IIRC the reason why it uses __i686 is because 586 and before does not
need to worry about the return stack
On Mon, May 2, 2011 at 11:49, Andrew Pinski pins...@gmail.com wrote:
On Sat, Apr 30, 2011 at 2:14 PM, Chris Demetriou c...@google.com wrote:
Makes -S output more easily preprocessable -- otherwise, the __i686 in
__i686.get_pc_think.reg chokes things.
IIRC the reason why it uses __i686 is
Makes -S output more easily preprocessable -- otherwise, the __i686 in
__i686.get_pc_think.reg chokes things.
bootstrapped x86_64-linux for C/C++ native on Ubunutu Lucid (x86-64),
no diff in testsuite output before/after.
(c, c++, libgomp, libmudflap, libstdc++ tested.)
Also manually tested:
