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/33256] internal compiler error: in print_operand_reloc, at config/mips/mips.c:5579



------- Comment #18 from richard at codesourcery dot com  2007-09-05 21:44 -------
Subject: Re:  internal compiler error: in print_operand_reloc, at
config/mips/mips.c:5579

"ddaney at avtrex dot com" <gcc-bugzilla@gcc.gnu.org> writes:
> richard at codesourcery dot com wrote:
>> ------- Comment #16 from richard at codesourcery dot com  2007-09-05 21:22 -------
>> Subject: Re:  internal compiler error: in print_operand_reloc, at
>> config/mips/mips.c:5579
>> 
>> "ddaney at avtrex dot com" <gcc-bugzilla@gcc.gnu.org> writes:
>>> My concern was that the bug only occurs for me with -EB, so running the 
>>> test case with -EL would be pointless.  I understand that you do most of 
>>> your testing on the simulator, but for someone doing testing on little 
>>> endian hardware there is no coverage without the -EB.
>> 
>> OK.  As I said before, I didn't think it would be pointless, because
>> we do want to make sure this continues to work for -EL too.
>
> The only time loading the low order bits of a word is done at an offset 
> from the base of the word is in big endian.  So I don't think it will 
> ever fail on a little endian system, but I may be missing something.

Yes, I realise that, but I meant that you can't really assume very much
about -mabi=64 -msym32 -EL at all from a mips{64,}{,-el}-linux-gnu run.
At least allowing the test to be run in little-endian would have provided
some coverage, and people were still going to notice if the -EB case
regressed.

Richard


-- 


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


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