public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Michael LIAO <michael.hliao@gmail.com>
Cc: autoconf@gnu.org, gcc@gcc.gnu.org, x32-abi@googlegroups.com,
	config-patches@gnu.org
Subject: Re: new triplet for x32 psABI?
Date: Wed, 12 Oct 2011 22:14:00 -0000	[thread overview]
Message-ID: <201110121129.46115.vapier@gentoo.org> (raw)
In-Reply-To: <CAO-CJbi9ciWRXSGZEfwKZpR1ajmts1SmDqN_hSW=h7Luf=sLaQ@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1004 bytes --]

On Wednesday 12 October 2011 01:03:19 Michael LIAO wrote:
> I am not asking a dedicated triplet for x32 to be used exclusively for
> x32 package build. I am asking additional triplet with enough details
> of execution environment (ABI definitely a necessary detail.) for
> package which relies on triplet to tell that. At least that triplet
> could be canonical and widely accepted for package really caring about
> that instead of forcing all package checking compiler options. If a
> package needs to support similar thing to mutlilib just like glibc,
> that new triplet will simiplifies their decision.

> gcc definitely is not that kind of package as it could be built to
> support generate x86-64, x32 and i386 code with the same package and
> need a runtime option to tell that.

except that if gcc doesn't change its default ABI output, it doesn't make it 
terribly useful.  you still need to specify the -mabi flag whenever you execute 
gcc, thus the tuple is just noise.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-10-12 15:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03 22:26 Michael LIAO
2011-10-03 22:30 ` Eric Blake
2011-10-03 22:35 ` Mike Frysinger
2011-10-03 22:57   ` Michael LIAO
2011-10-03 23:04     ` Mike Frysinger
2011-10-03 23:48       ` Michael LIAO
2011-10-04  0:47         ` Mike Frysinger
2011-10-04  3:26           ` Michael LIAO
2011-10-04  3:56             ` Mike Frysinger
2011-10-04  0:54         ` H.J. Lu
2011-10-04  3:44           ` Michael LIAO
2011-10-04 19:53             ` H.J. Lu
2011-10-03 23:06     ` H.J. Lu
2011-10-12  4:49   ` Michael LIAO
2011-10-12  7:13     ` Mike Frysinger
2011-10-12  7:27       ` Michael LIAO
2011-10-12 22:14         ` Mike Frysinger [this message]
2011-10-13  0:49         ` H.J. Lu
2011-10-13  7:26           ` Mike Frysinger

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=201110121129.46115.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=autoconf@gnu.org \
    --cc=config-patches@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=michael.hliao@gmail.com \
    --cc=x32-abi@googlegroups.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).