public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hezekiahehud at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46275] -masm=intel -fPIC causes global offset table issues
Date: Tue, 02 Nov 2010 18:54:00 -0000	[thread overview]
Message-ID: <20101102185400._2IpSdHvxSHzkv6d-BRtwwBFFSblesRNwpTlnG5nyiU@z> (raw)
In-Reply-To: <bug-46275-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from hezekiahehud at gmail dot com 2010-11-02 18:53:55 UTC ---
Apologies for the severity change, Andrew.  Shortly after filing the bug, I saw
the severity was "normal" and thought perhaps the system had glitched or I had
forgotten to set that field of the form.  I didn't see the email showing you
had altered the severity until after I had bumped it to "major" again.

That being said, company I work for is attempting to complete a 32-bit Linux
port of our primary product wholly using GCC (we are currently using a GCC and
Intel compiler mix), and -masm=intel is an unavoidable requirement for our
code.  This bug is a serious problem for us.  I defer to your judgement on the
relevant severity of bugs, but please realise that this has considerably more
impact than the simple "hello, world" example I gave.


  parent reply	other threads:[~2010-11-02 18:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 18:30 [Bug c/46275] New: " hezekiahehud at gmail dot com
2010-11-02 18:30 ` [Bug c/46275] " hezekiahehud at gmail dot com
2010-11-02 18:31 ` [Bug target/46275] " pinskia at gcc dot gnu.org
2010-11-02 18:33 ` hezekiahehud at gmail dot com
2010-11-02 18:35 ` hezekiahehud at gmail dot com
2010-11-02 18:40 ` pinskia at gcc dot gnu.org
2010-11-02 18:54 ` hezekiahehud at gmail dot com [this message]
2010-11-02 18:59 ` pinskia at gcc dot gnu.org
2010-11-02 19:08 ` hezekiahehud at gmail dot com
2010-11-02 21:07 ` ubizjak at gmail dot com
2010-11-03  8:48 ` ubizjak at gmail dot com
2010-11-03 14:03 ` hjl.tools at gmail dot com
2010-11-03 14:13 ` hezekiahehud at gmail dot com

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=20101102185400._2IpSdHvxSHzkv6d-BRtwwBFFSblesRNwpTlnG5nyiU@z \
    --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).