public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gregnietsky at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/56031] New: Set ABI/Multilib to x32 when targeting x86_64-*-gnux32 Date: Fri, 18 Jan 2013 13:54:00 -0000 [thread overview] Message-ID: <bug-56031-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56031 Bug #: 56031 Summary: Set ABI/Multilib to x32 when targeting x86_64-*-gnux32 Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: gregnietsky@gmail.com Created attachment 29206 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29206 Set native ABI to x32 when x86-64-*-gnux32 is targeted and no --with-abi is given When building native non multilib x86_64-*-gnux32 target you have to supply --with-abi=x32 this is not intuitive and IMHO should be default and not need be supplied. the attached patch sets with-abi and sets native x32 if configured target is x86_64-*-gnux32 and with-abi is not set. i personally feel that this target may include 32/64 multilibs but should always be native x32 to build it native 64 passing --with-abi=64 is required the multilib-list option does not have any effect.
reply other threads:[~2013-01-18 13:54 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-56031-4@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: linkBe 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).