public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/26885]  New: [4.1/4.2 regression] -m64 -m32 no longer creates 32-bit object
Date: Mon, 27 Mar 2006 14:51:00 -0000	[thread overview]
Message-ID: <bug-26885-87@http.gcc.gnu.org/bugzilla/> (raw)

Up until
2005-06-13  Mark Mitchell  <mark@codesourcery.com>

        * config/i386/x86-64.h (ASM_SPEC): Explicitly pass --64 to the
        assembler in 64-bit mode.
change -m64 -m32 used to work on x86_64 (I know it is quite fragile and
on many arches doesn't DTRT), but now as the asm spec has:
%{m32:--32} %{-m64:--64} we for both -m64 -m32 and -m32 -m64 end up with
--32 --64 being passed to the assembler (in that order).

Guess best would be to say in *.opt rather than RejectNegative what the
negative
of the option is (for m32 Negative(m64) and for m64 Negative(m32) or something
like that) and handle this in gcc.c/opts.c.


-- 
           Summary: [4.1/4.2 regression] -m64 -m32 no longer creates 32-bit
                    object
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jakub at gcc dot gnu dot org
GCC target triplet: x86_64-linux


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


             reply	other threads:[~2006-03-27 14:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27 14:51 jakub at gcc dot gnu dot org [this message]
2006-03-27 16:37 ` [Bug target/26885] " pinskia at gcc dot gnu dot org
2006-03-28  8:20 ` jakub at gcc dot gnu dot org
2006-03-31  2:52 ` mmitchel at gcc dot gnu dot org
2006-04-06 13:27 ` jakub at gcc dot gnu dot org
2006-04-16 19:11 ` mmitchel at gcc dot gnu dot org
2006-04-22  0:43 ` pinskia at gcc dot gnu dot org
2006-04-22  1:16 ` pinskia at physics dot uc dot edu
2006-04-22 15:34 ` hjl at lucon dot org
2006-04-23  2:24 ` pinskia at gcc dot gnu dot org
2006-05-16  5:52 ` mmitchel at gcc dot gnu dot org
2006-05-16 14:27 ` hjl at gcc dot gnu dot org
2006-05-16 16:33 ` hjl at lucon dot org
2006-05-16 16:51 ` mark at codesourcery dot com
2006-05-16 17:07 ` hjl at gcc dot gnu dot org
2006-05-16 17:29 ` pinskia at gcc dot gnu dot org
2006-05-16 17:39 ` hjl at lucon dot org
2006-05-16 17:41 ` pinskia at gcc dot gnu dot org
2006-05-16 21:30 ` bernds_cb1 at t-online dot de
2006-05-16 21:46 ` mmitchel at gcc dot gnu dot org
2006-05-17 15:37 ` mmitchel at gcc dot gnu dot org
2006-05-25  2:35 ` mmitchel at gcc dot gnu dot org
2006-07-05  9:05 ` [Bug target/26885] [4.1 " pinskia at gcc dot gnu dot org
2007-02-14  9:01 ` mmitchel at gcc dot gnu dot org
2008-07-04 15:25 ` jsm28 at gcc dot gnu dot 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-26885-87@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).