public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "poirierg at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/29440] 4.2 20061007 experimental misscompiles libavcodec/h264.o Date: Thu, 12 Oct 2006 14:53:00 -0000 [thread overview] Message-ID: <20061012145301.8162.qmail@sourceware.org> (raw) In-Reply-To: <bug-29440-9939@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from poirierg at gmail dot com 2006-10-12 14:53 ------- Hello, (In reply to comment #3) > Does it work when compiled with -O0 instead of -O4? How about -O1? The code compiles and produces the expected result with -O1, O2, but can't be compiled with -O0: In file included from h264.c:36: cabac.h: In function 'get_cabac': cabac.h:454: error: can't find a register in class 'GENERAL_REGS' while reloading 'asm' cabac.h:454: error: 'asm' operand has impossible constraints h264.c: In function 'decode_cabac_residual': h264.c:6120: warning: initialization from incompatible pointer type > Besies above, I noticed that the asm in get_cabac looks to be clobbering memory > but is not marked as such. I can't really comment on that as I'm not too inline-asm fluent... however, I can say that this code can't be compiled without -fomit-frame-pointer. Is GCC supposed to produce valid code with this source to begin with? Guillaume -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29440
next prev parent reply other threads:[~2006-10-12 14:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-12 14:23 [Bug c/29440] New: 4.2 20061007 experiemental " poirierg at gmail dot com 2006-10-12 14:26 ` [Bug c/29440] " poirierg at gmail dot com 2006-10-12 14:28 ` poirierg at gmail dot com 2006-10-12 14:30 ` [Bug middle-end/29440] 4.2 20061007 experimental " pinskia at gcc dot gnu dot org 2006-10-12 14:34 ` pinskia at gcc dot gnu dot org 2006-10-12 14:40 ` pluto at agmk dot net 2006-10-12 14:53 ` poirierg at gmail dot com [this message] 2006-10-12 15:03 ` poirierg at gmail dot com 2006-10-13 7:37 ` poirierg 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=20061012145301.8162.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: 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).