Hi,
After pro and epilogue pass I have the following epilogue insn:
(insn/f 20 19 21 2 (parallel [
(set (mem:DI (plus:SI (reg:SI 26 r26)
(reg/f:SI 57 r57)) [0 S8 A8])
(reg:DI 57 r57))
(set (reg/f:SI 57 r57)
(plus:SI (r
Occasionally I try to run GCC tests using flags for which I don't have
the required target platform, or even compatible libraries. I usually
hack up several test files to kind of get what I want, but it's a pain.
Right now, for example, I'm trying to run upstream gcc.target/arm tests
for several s
On Wed, Dec 19, 2012 at 2:32 AM, Joel Sherrill
wrote:
> My primary concern centers whether any 386 w/o fpu IP cores or space hardened
> i386dx/sx or 486sx CPUs are impacted. These could be used in new designs.
>
> This also eliminates gcc from use on any older embedded x86 boards w/o fpu.
AFAICT
On 12/19/2012 4:13 PM, Janne Blomqvist wrote:
On Wed, Dec 19, 2012 at 2:32 AM, Joel Sherrill
wrote:
My primary concern centers whether any 386 w/o fpu IP cores or space hardened
i386dx/sx or 486sx CPUs are impacted. These could be used in new designs.
This also eliminates gcc from use on any
In bug 55237, Uros suggested to implement shortcuts from the like of
http://gcc.gnu.org/r194572
to
http://gcc.gnu.org/viewcvs?view=revision&revision=194572
I implemented this now, but before making this a new standard, I
did want to ask here whether any of you have concerns or suggestions
aro
