public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/56975] [regression] dllimport broken on i686-pc-cygwin Date: Tue, 16 Apr 2013 09:37:00 -0000 [thread overview] Message-ID: <bug-56975-4-EedMfhUR1e@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56975-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56975 Kai Tietz <ktietz at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ktietz at gcc dot gnu.org --- Comment #1 from Kai Tietz <ktietz at gcc dot gnu.org> 2013-04-16 09:37:38 UTC --- Hmm, as this bug seems not to happen for mingw 32-bit, it might be related to definition of DEFAULT_ABI for 32-bit. Does it help to set in cygming.h header the line '#define DEFAULT_ABI (TARGET_64BIT ? MS_ABI : SYSV_ABI)' to '#define DEFAULT_ABI (TARGET_64BIT ? MS_ABI : MS_ABI)' ? If so, we need an new definition to indicate pe-coff ABI instead. At some places we are using here check DEFAULT_ABI == MS_ABI etc, which might cause for 32-bit here the issue. See for example the code in predicate.md, i386.c, etc.
next prev parent reply other threads:[~2013-04-16 9:37 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-16 8:00 [Bug target/56975] New: " davek at gcc dot gnu.org 2013-04-16 9:37 ` ktietz at gcc dot gnu.org [this message] 2013-04-17 2:31 ` [Bug target/56975] " alexpux at gmail dot com 2013-04-18 15:58 ` jojelino at gmail dot com 2013-04-18 18:19 ` ktietz at gcc dot gnu.org 2013-04-19 4:56 ` alexpux at gmail dot com 2013-04-19 8:18 ` ktietz at gcc dot gnu.org 2013-04-19 14:26 ` jojelino at gmail dot com 2013-04-19 18:18 ` davek at gcc dot gnu.org 2013-04-21 10:12 ` alexpux at gmail dot com 2013-05-13 19:52 ` ktietz 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-56975-4-EedMfhUR1e@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).