This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/49746] Generated PA-RISC2.0w code cannot be assembled by GNU as-2.21.1
- From: "h.m.brand at xs4all dot nl" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 15 Jul 2011 07:40:40 +0000
- Subject: [Bug target/49746] Generated PA-RISC2.0w code cannot be assembled by GNU as-2.21.1
- Auto-submitted: auto-generated
- References: <bug-49746-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49746
--- Comment #4 from H.Merijn Brand <h.m.brand at xs4all dot nl> 2011-07-15 07:39:01 UTC ---
On Thu, 14 Jul 2011 20:34:46 +0000, "sje at cup dot hp.com"
<gcc-bugzilla@gcc.gnu.org> wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49746
>
> Steve Ellcey <sje at cup dot hp.com> changed:
>
> --- Comment #2 from Steve Ellcey <sje at cup dot hp.com> 2011-07-14 20:34:28 UTC ---
> Are you trying to use a 32 bit GCC to bootstrap a 64 bit GCC?
No, a full 64bit gcc-3.4.6
> I see you have CC set to gcc64 which makes me think that you are using
gcc32 is a symlink to /usr/local/pa20_32/bin/gcc
gcc64 is a symlink to /usr/local/pa20_64/bin/gcc
While building gcc-4.6.1, I made sure /usr/local/pa20_64/bin is in the
front of my $PATH
> a 64 bit GCC to do the bootstrap but you have -mpa-risc-2-0 in CFLAGS,
I do so because I know some configurations store the flags to be used
later by other applications. If this is a problem, I'll leave it off.
> which I think means the 32 bit 2.0 instruction set and I don't think it
> should be used for 64 bit builds.
>
> Can you bootstrap if you leave off the -mpa-risc-2-0 flag?
I'll try