From: Jan Hubicka <jh@suse.cz>
To: Bo Thorsen <bo@sonofthor.dk>
Cc: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>,
gcc@gcc.gnu.org, jh@suse.cz
Subject: Re: bogus .quad in i386/att.h
Date: Wed, 10 Oct 2001 12:01:00 -0000 [thread overview]
Message-ID: <20011010210045.B27461@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <01100911481107.00797@idefix>
> > ..quad is definitely not something supported by the AT&T-derived
> > assemblers. Maybe it's a GAS thing and should be in gas.h. Maybe it's
> > an x86-64 thing and should be in x86-64.h. But att.h sure seems like
> > the wrong place for it. This does show up as testsuite failures.
> >
> > Can you please move this?
>
> I don't know why Jan re-introduced this, it wasn't in the last patch I sent
> before going on vacation. I tested x86-64 compilation without the att.h patch
> (which was included in the first time I sent the patch) and it seemed to
> work. Jan can you comment on why you added it again?
The idea was that we need some ASM_QUAD definition in order to compile w/o
extra ifdef garbage around. The ASM_QUAD will be used only for 64bit compilation
att.h looked like right place to do, as all currently supported assemblers are
derivation of it and even when there isn't official att assembler for x86_64.
Honza
next prev parent reply other threads:[~2001-10-10 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 18:42 Billinghurst, David (CRTS)
2001-10-08 18:59 ` Robert Lipe
2001-10-09 2:49 ` Bo Thorsen
2001-10-10 12:01 ` Jan Hubicka [this message]
2001-10-10 12:22 ` Robert Lipe
2001-10-10 12:24 ` Jan Hubicka
2001-10-10 13:30 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2001-10-08 18:34 Robert Lipe
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=20011010210045.B27461@atrey.karlin.mff.cuni.cz \
--to=jh@suse.cz \
--cc=David.Billinghurst@riotinto.com \
--cc=bo@sonofthor.dk \
--cc=gcc@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).