https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901
Maciej W. Rozycki changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ma...@linux-mips.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901
--- Comment #8 from CVS Commits ---
The master branch has been updated by Maciej W. Rozycki :
https://gcc.gnu.org/g:a27d5f9a73978f20cfef1796a94f6a1a82438146
commit r11-5761-ga27d5f9a73978f20cfef1796a94f6a1a82438146
Author: Matt Thomas
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901
coypu changed:
What|Removed |Added
CC||coypu at sdf dot org
--- Comment #7 from coypu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901
--- Comment #6 from Martin Husemann ---
This is beyound my gcc capabilities: the rtx in question is wrong for vax, but
the bug seems to be at a higher level: an indexed memory access can not be
wrapped into a subreg with offset in the same stateme
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901
--- Comment #5 from Martin Husemann ---
Created attachment 31275
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31275&action=edit
.i file from the failing compile
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901
--- Comment #4 from Martin Husemann ---
I got a quick lesson in addressing modes for vax ;-)
It seems the mode = HImode passed to the upper functions in the call stack is
the problem - with HImode we can only use index operands with a factor of 2,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901
--- Comment #3 from Martin Husemann ---
Matt asked for the instruction involved - I think it is this:
(insn 245 244 246 51 (set (mem:HI (reg/v/f:SI 1 %r1 [orig:67 sup ] [67]) [2
*sup_104+0 S2 A16])
(plus:HI (subreg:HI (mem/u/c:SI (plus:SI
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901
--- Comment #2 from Martin Husemann ---
indexable_address_p() returns false for
(symbol_ref:SI ("DECPOWERS") [flags 0x40] )
because flag_pic is true and symbolic_operand (xfoo0, SImode)) returns true:
/* Return true if xfoo0 and xfoo1 constitut
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901
--- Comment #1 from Martin Husemann ---
The real question is: why does memory_address_addr_space_p() return false for
this rtx. Stepping into it results in:
0x007618be in vax_legitimate_address_p (mode=HImode, x=0x7ea0fd2c,
strict=20, 5, 212
10 matches
Mail list logo