public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/45160] [4.4.x/4.5.x regression] Invalid assembly code is generated for x86 architecture for faad2 library (AAC decode algorithm)
Date: Mon, 02 Aug 2010 16:21:00 -0000	[thread overview]
Message-ID: <20100802162119.15425.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45160-5637@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from pinskia at gcc dot gnu dot org  2010-08-02 16:21 -------
> Like I said GCC 4.2.x has no problems compiling this library, so I have no idea
> who to blame and who else I should get in touch with.

I would get into contact with the developers of the library first.  Yes GCC has
some bugs but the library could have a bug still.  Since the problem disappreas
with -fno-strict-aliasing that normally points at a bug in the library.  In
that it does not follow the C/C++ alisaing rules.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


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


  parent reply	other threads:[~2010-08-02 16:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-01 23:59 [Bug inline-asm/45160] New: [GCC 4.4.x " t dot artem at mailcity dot com
2010-08-02  0:09 ` [Bug inline-asm/45160] " t dot artem at mailcity dot com
2010-08-02  0:31 ` t dot artem at mailcity dot com
2010-08-02 13:09 ` [Bug inline-asm/45160] [4.4.x/4.5.x " t dot artem at mailcity dot com
2010-08-02 13:10 ` t dot artem at mailcity dot com
2010-08-02 13:15 ` t dot artem at mailcity dot com
2010-08-02 14:12 ` rguenth at gcc dot gnu dot org
2010-08-02 15:49 ` t dot artem at mailcity dot com
2010-08-02 16:21 ` pinskia at gcc dot gnu dot org [this message]
2010-08-02 20:27 ` t dot artem at mailcity dot com
2010-08-30 15:47 ` rguenth at gcc dot gnu dot org
2010-09-06 20:20 ` t dot artem at mailcity 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=20100802162119.15425.qmail@sourceware.org \
    --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).