On 14-Apr-13, at 7:37 AM, Steven Bosscher wrote:
On Tue, Apr 9, 2013 at 3:46 AM, John David Anglin wrote:
Seems to cause a reload problem:
Problem may be in not removing the continuation character \ from
various
macro definitions.
Right, ASM_OUTPUT_ADDR_VEC_ELT and
On Sun, May 5, 2013 at 10:50 PM, John David Anglin wrote:
Committed the attached version after testing on hppa2.0w-hp-hpux11.11 and
hppa64-hp-hpux11.11.
Thanks for working on this!
Ciao!
Steven
On 14-Apr-13, at 7:37 AM, Steven Bosscher wrote:
On Tue, Apr 9, 2013 at 3:46 AM, John David Anglin wrote:
Seems to cause a reload problem:
Problem may be in not removing the continuation character \ from
various
macro definitions.
Right, ASM_OUTPUT_ADDR_VEC_ELT and
On Tue, Apr 9, 2013 at 3:46 AM, John David Anglin wrote:
Seems to cause a reload problem:
Problem may be in not removing the continuation character \ from various
macro definitions.
Right, ASM_OUTPUT_ADDR_VEC_ELT and ASM_OUTPUT_ADDR_DIFF_ELT had a
trailing '\' that I should have removed. And
On Sat, Apr 6, 2013 at 9:29 PM, John David Anglin wrote:
-mno-big-switch
can go. Probably, nobody will notice...
Like in the attached patch. My PA box appears to have joined the
silicon grave yard last night while trying to bootstrap this patch, so
I could use some help testing this while I'm
Hello,
I'm trying to get to a point where the CFG is useable even in the
delay-slot filling pass (dbr_schedule) and I'm currently stuck on a
transformation that the PA port does if -mno-big-switch is in effect.
With !TARGET_BIG_SWITCH, the PA port explodes a JUMP_TABLE_DATA to
real code, i.e.
On 6-Apr-13, at 12:25 PM, Steven Bosscher wrote:
Are there any reasons against removing !TARGET_BIG_SWITCH support? It
would really help if this code can go away...
Yes, branch distances are limited to what can be encoded in a 17-bit
pc relative
offset. Large code will break with
On Sat, Apr 6, 2013 at 7:09 PM, John David Anglin wrote:
On 6-Apr-13, at 12:25 PM, Steven Bosscher wrote:
Are there any reasons against removing !TARGET_BIG_SWITCH support? It
would really help if this code can go away...
Yes, branch distances are limited to what can be encoded in a
17-bit
On 6-Apr-13, at 3:16 PM, Steven Bosscher wrote:
On Sat, Apr 6, 2013 at 7:09 PM, John David Anglin wrote:
On 6-Apr-13, at 12:25 PM, Steven Bosscher wrote:
Are there any reasons against removing !TARGET_BIG_SWITCH support?
It
would really help if this code can go away...
Yes, branch
