From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Uros Bizjak <ubizjak@gmail.com>
Subject: Re: PATCH: PR target/60151: HAVE_AS_GOTOFF_IN_DATA is mis-detected on x86-64
Date: Tue, 11 Feb 2014 20:29:00 -0000 [thread overview]
Message-ID: <ydda9dxe6lv.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <CAMe9rOqq2qZ8RYjCTXJ0tsbZ976EAJ0D_4+DGX-Z3FpkoqDzKg@mail.gmail.com> (H. J. Lu's message of "Tue, 11 Feb 2014 12:03:03 -0800")
"H.J. Lu" <hjl.tools@gmail.com> writes:
> On Tue, Feb 11, 2014 at 11:40 AM, Rainer Orth
> <ro@cebitec.uni-bielefeld.de> wrote:
>> Hi H.J.,
>>
>>> HAVE_AS_GOTOFF_IN_DATA defines a 32-bit assembler feature, we need to
>>> pass --32 to assembler. Otherwise, we get the wrong result on x86-64.
>>> We already pass --32 to assembler on x86. It should be OK to do it
>>> in configure. OK for trunk?
>>
>> This would break Solaris/x86 with as configurations, where this test
>> currently passes, but would fail since as doesn't understand --32.
>>
>
> How about passing --32 to as only for Linux? OK to install?
I'd rather do it for gas instead, which can be used on non-Linux
systems, too.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2014-02-11 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 19:28 H.J. Lu
2014-02-11 19:41 ` Rainer Orth
2014-02-11 20:03 ` H.J. Lu
2014-02-11 20:29 ` Rainer Orth [this message]
2014-02-11 20:41 ` H.J. Lu
2014-02-12 8:20 ` Uros Bizjak
2014-02-12 16:13 ` H.J. Lu
2014-02-11 19:41 ` Uros Bizjak
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=ydda9dxe6lv.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=ubizjak@gmail.com \
/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).