public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/59824] [4.9 Regression] r206418 miscompiles ffmpeg
Date: Wed, 15 Jan 2014 12:10:00 -0000	[thread overview]
Message-ID: <bug-59824-4-7StIlEqEun@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59824-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
 gcc --save-temps -g -I. -I./ -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC
-DHAVE_AV_CONFIG_H -std=c99 -fomit-frame-pointer -fPIC -pthread -D_GNU_SOURCE=1
-D_REENTRANT -I/usr/include/SDL -g -Wdeclaration-after-statement -Wall
-Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wwrite-strings
-Wtype-limits -Wundef -Wmissing-prototypes -Wno-pointer-to-int-cast
-Wstrict-prototypes -Wno-parentheses -Wno-switch -Wno-format-zero-length
-Wno-pointer-sign -O3 -fno-math-errno -fno-signed-zeros -fno-tree-vectorize
-Werror=implicit-function-declaration -Werror=missing-prototypes
-Werror=return-type -Werror=vla -Wno-maybe-uninitialized -MMD -MF
libavcodec/mpeg4video.d -MT libavcodec/mpeg4video.o -c -o
libavcodec/mpeg4video.o libavcodec/mpeg4video.c


  parent reply	other threads:[~2014-01-15 12:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 11:52 [Bug middle-end/59824] New: " trippels at gcc dot gnu.org
2014-01-15 11:53 ` [Bug middle-end/59824] " trippels at gcc dot gnu.org
2014-01-15 12:10 ` trippels at gcc dot gnu.org [this message]
2014-01-15 12:26 ` trippels at gcc dot gnu.org
2014-01-15 12:27 ` trippels at gcc dot gnu.org
2014-01-15 12:41 ` jakub at gcc dot gnu.org
2014-01-15 13:11 ` trippels 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-59824-4-7StIlEqEun@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: 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).