From: Ali Abdul Ghani <blade.vp2020@gmail.com>
To: Giuseppe Caizzone <acaizzo@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Does ada work on x32 currently (gcc 5.x)?
Date: Sun, 26 Jul 2015 21:21:00 -0000 [thread overview]
Message-ID: <CAHWa5udGtqqMccKH4_7JrnpzhwJ7JrgP3x1Z1BQDB4T8PTycxg@mail.gmail.com> (raw)
In-Reply-To: <CA+3Kdve3N-WdZZpFFwhjuMpf0tWXt-u8zBmg=t5=o0tEN6AKNw@mail.gmail.com>
its same for me
2015-07-25 0:48 جرينتش-07:00, Giuseppe Caizzone <acaizzo@gmail.com>:
> Hello,
>
> I've been unable to bootstrap gcc 5.[12], starting from gcc 4.9.2, if
> I configure it with --with-abi=mx32 and having "ada" among the values
> for --enable-languages; searching the web I've found some old mailing
> list messages about ada not working on x32 (however gcc 4.9.x at least
> did complete the bootstrap under the same conditions). Is it still the
> case that ada isn't supported on x32 (and therefore I should drop ada
> from the language list for x32) or it's supposed to work instead (and
> therefore I can invest some more time finding out what I'm doing
> wrong)?
>
> Thanks,
> Giuseppe
>
> (In case it's of interest, what *I think* happens on my particular
> machine is that the stage2 gnat1 binary fails with EFAULT when ran
> during the bootstrap because it passes a wrong pointer to the write
> syscall; the pointer has in its lower 32 bits the correct address it's
> supposed to have, but other stuff in the upper bits. The stage1
> binary, instead, is fine in this respect. Also, gcc 4.9.2 does
> bootstrap successfully on the same box with the same configure
> parameters. I don't know if this is due to a bug or rather a
> misconfiguration of my system.)
>
--
Think not of them, thou hast thy music too
prev parent reply other threads:[~2015-07-26 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 7:48 Giuseppe Caizzone
2015-07-26 21:21 ` Ali Abdul Ghani [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHWa5udGtqqMccKH4_7JrnpzhwJ7JrgP3x1Z1BQDB4T8PTycxg@mail.gmail.com \
--to=blade.vp2020@gmail.com \
--cc=acaizzo@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).