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 tree-optimization/59644] [4.9 Regression] r206243 miscompiles Linux kernel
Date: Tue, 31 Dec 2013 08:17:00 -0000	[thread overview]
Message-ID: <bug-59644-4-EgsBxA3Sc4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59644-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
kernel/printk/printk.o gets miscompiled.

 % gcc -Wp,-MD,kernel/printk/.printk.o.d  -nostdinc -isystem
/var/tmp/gcc_test_/usr/local/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.9.0/include
-I/var/tmp/linux/arch/x86/include -Iarch/x86/include/generated  -Iinclude
-I/var/tmp/linux/arch/x86/include/uapi -Iarch/x86/include/generated/uapi
-I/var/tmp/linux/include/uapi -Iinclude/generated/uapi -include
/var/tmp/linux/include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
-Werror-implicit-function-declaration -Wno-format-security
-fno-delete-null-pointer-checks -O2 -m64 -mno-mmx -mno-sse
-mpreferred-stack-boundary=3 -march=native -mno-red-zone -mcmodel=kernel
-funit-at-a-time -maccumulate-outgoing-args -DCONFIG_AS_CFI=1
-DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1
-DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare
-fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx
-Wframe-larger-than=1024 -fno-stack-protector -Wno-unused-but-set-variable
-fomit-frame-pointer -Wdeclaration-after-statement -Wno-pointer-sign
-fno-strict-overflow -fconserve-stack -Werror=implicit-int
-Werror=strict-prototypes -DCC_HAVE_ASM_GOTO    -D"KBUILD_STR(s)=#s"
-D"KBUILD_BASENAME=KBUILD_STR(printk)"  -D"KBUILD_MODNAME=KBUILD_STR(printk)"
-c -o kernel/printk/printk.o kernel/printk/printk.c --save-temps


  parent reply	other threads:[~2013-12-31  8:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-30 23:03 [Bug tree-optimization/59644] New: " trippels at gcc dot gnu.org
2013-12-30 23:43 ` [Bug tree-optimization/59644] " jakub at gcc dot gnu.org
2013-12-31  8:17 ` trippels at gcc dot gnu.org [this message]
2013-12-31  8:18 ` trippels at gcc dot gnu.org
2013-12-31  8:19 ` trippels at gcc dot gnu.org
2013-12-31  8:20 ` trippels at gcc dot gnu.org
2013-12-31  8:26 ` trippels at gcc dot gnu.org
2013-12-31 11:47 ` jakub at gcc dot gnu.org
2013-12-31 13:03 ` trippels at gcc dot gnu.org
2014-01-06  8:21 ` trippels at gcc dot gnu.org
2014-01-06  8:48 ` trippels at gcc dot gnu.org
2014-01-06  9:08 ` jakub at gcc dot gnu.org
2014-01-06  9:17 ` trippels at gcc dot gnu.org
2014-01-06  9:26 ` jakub at gcc dot gnu.org
2014-01-06  9:36 ` trippels at gcc dot gnu.org
2014-01-06 10:00 ` trippels at gcc dot gnu.org
2014-01-06 10:04 ` trippels at gcc dot gnu.org
2014-01-06 10:09 ` hjl.tools at gmail dot com
2014-01-06 10:12 ` jakub at gcc dot gnu.org
2014-01-06 10:21 ` trippels at gcc dot gnu.org
2014-01-06 11:28 ` jakub at gcc dot gnu.org
2014-01-06 11:55 ` jakub at gcc dot gnu.org
2014-01-06 13:39 ` [Bug target/59644] " jakub at gcc dot gnu.org
2014-01-06 21:38 ` jakub at gcc dot gnu.org
2014-01-06 21:39 ` jakub 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-59644-4-EgsBxA3Sc4@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).