From: Robert Lipe <robertlipe@usa.net>
To: gcc@gcc.gnu.org
Cc: jh@suze.cz
Subject: Re: bogus .quad in i386/att.h
Date: Mon, 08 Oct 2001 18:59:00 -0000 [thread overview]
Message-ID: <20011008210246.X3630@rjlhome.caldera.com> (raw)
In-Reply-To: <8D00C32549556B4E977F81DBC24E985D40FFAA@crtsmail1.technol_exch.corp.riotinto.org>
David> and it broke cygwin bootstrap
David> http://gcc.gnu.org/ml/gcc-bugs/2001-10/msg00084.html
Good point.
Jan> I am not quite sure if it is cleaner to ifdef around each ASM_QUAD
Jan> use, or if we can just define ASM_QUAD to ".quad" everywhere...
Well, ".quad" is definitely not part of the standard AT&T assembler
syntax. Elsewhere in the compiler, it already knows how to do this
anyway. Isn't that what UNALGINED_DOUBLE_INT_ASM_OP is about?
Why invent something new here?
RJL
>
> -----Original Message-----
> From: Robert Lipe [ mailto:robertlipe@usa.net ]
> Sent: Tuesday, 9 October 2001 11:38
> To: gcc@gcc.gnu.org
> Cc: jh@suze.cz
> Subject: bogus .quad in i386/att.h
>
>
> Jan, your commit that starts:
>
> Tue Oct 2 12:46:01 CEST 2001 Bo Thorsen <bo@suse.co.uk>,
> Andreas Jaeger <aj@suse.de>,
> Jan Hubicka <jh@suse.cz>
>
> * doc/invoke.texi (i386 Options): Document x86-64 options.
> (i386 and x86-64 Options): Rename i386 options section.
>
>
> added an entry for ASM_QUAD in att.h. But the ChangeLog does not
> call out any change to att.h.
>
> ..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?
>
> Thank you,
> RJL
next prev parent reply other threads:[~2001-10-08 18:59 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 [this message]
2001-10-09 2:49 ` Bo Thorsen
2001-10-10 12:01 ` Jan Hubicka
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=20011008210246.X3630@rjlhome.caldera.com \
--to=robertlipe@usa.net \
--cc=gcc@gcc.gnu.org \
--cc=jh@suze.cz \
/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).