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/10129] Ada bootstrap fails on PPC-Darwin - invalid assembler emitted - PIC related


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From pinskia at physics dot uc dot edu  2003-07-02 16:43 -------
I think the reason why machopic_function_base_name was done the way without a hashtable was 
because the frontend Apple supported had the conversion to rtl interwoven so Apple only tested it 
with c, objective-c and c++.  But as we saw other frontends the conversion to rtl is interwoven but 
I do not really know if the Ada frontend is right to do this but I only working around the problem in 
Darwin's backend and removing the constraint of the rtl have been not interwoven.  
I wish someone figure out who is right here, I think the Ada frontend is right at what it is doing.

In fact I download the Ada compiler yesterday and get the first patch done within a hour.
The second one I had to figure out why the PIC labels were different between the one in the restore 
from the setjmp and the one in the function and that was just having gdb stop inside 
machopic_function_base_name when a label was generated and I say ali_scan_ali came up twice 
with another in between so I knew something was wrong (or right in the case for Ada) so I saw I 
could just store the function name and the label in a hashtable and lookup it up and see if there 
was alreay one there, I left the old way of finding the pic label so that the speed of gcc would not 
slow down too far.  I am running bootstrap right now on the patch but it should be past the old 
place of failure soon.


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