public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/52096] -dumpmachine does not respect -m32
Date: Thu, 02 Feb 2012 16:30:00 -0000	[thread overview]
Message-ID: <bug-52096-4-V4bl6SpGG8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52096-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52096

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-02-02 16:30:16 UTC ---
No, dumpmachine should dump the target which gcc was built.  It should not be
made multilib aware.

If you want to make sure you are compiling for 32bit, then check the
preprocessed predefines instead.


  reply	other threads:[~2012-02-02 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 16:27 [Bug driver/52096] New: " matze at braunis dot de
2012-02-02 16:30 ` pinskia at gcc dot gnu.org [this message]
2012-02-02 16:31 ` [Bug driver/52096] " pinskia at gcc dot gnu.org

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=bug-52096-4-V4bl6SpGG8@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).