public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dirk dot behme at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/27363] ARM gcc 4.1 optimization bug
Date: Wed, 07 Jun 2006 16:08:00 -0000 [thread overview]
Message-ID: <20060607155257.2942.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27363-12620@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from dirk dot behme at googlemail dot com 2006-06-07 15:52 -------
Created an attachment (id=11628)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11628&action=view)
.i file of pcm_native.c and .s files for -Os, -O1 and -O2
Attached the .i and .s for -Os & -O2 (failing) and -O1 (working) (generated
with --save-temps).
Used compile options (from Linux kernel 2.6.17-rc5):
arm-linux-gcc -Wp,-MD,sound/core/.pcm_native.o.d -nostdinc -isystem
/usr/arm/arm-linux_4_1_0/bin/../lib/gcc/arm-linux/4.1.0/include -D__KERNEL__
-Iinclude -include include/linux/autoconf.h -mlittle-endian -Wall -Wundef
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O1
-fno-omit-frame-pointer -fno-optimize-sibling-calls -fno-omit-frame-pointer
-mapcs -mno-sched-prolog -mabi=apcs-gnu -mno-thumb-interwork
-D__LINUX_ARM_ARCH__=5 -march=armv5te -mtune=arm9tdmi -msoft-float -Uarm
-Wdeclaration-after-statement -Wno-pointer-sign -DMODULE -D"KBUILD_STR(s)=#s"
-D"KBUILD_BASENAME=KBUILD_STR(pcm_native)"
-D"KBUILD_MODNAME=KBUILD_STR(snd_pcm)" --save-temps -c -o
sound/core/pcm_native.o sound/core/pcm_native.c
Only -O1 & -O2 & -Os were modified.
Small note:
While compiling only pcm_native.c with -O1 and using the resulting modules (4
modules depend on it) while using -Os for all other modules make the error I
observed go away. However, I get no sound output like if I compile all sound
modules with -O1. Seems that some other files of kernels sound system have (the
same?) optimization issue as well. But I think to start we should concentrate
on this file.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27363
next prev parent reply other threads:[~2006-06-07 15:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-30 4:48 [Bug c/27363] New: " nh26223 at yahoo dot com dot cn
2006-04-30 5:01 ` [Bug target/27363] " pinskia at gcc dot gnu dot org
2006-04-30 5:09 ` yfw dot debian at gmail dot com
2006-04-30 5:32 ` yfw dot debian at gmail dot com
2006-04-30 9:09 ` yfw dot debian at gmail dot com
2006-05-14 17:15 ` s_j_newbury at yahoo dot co dot uk
2006-06-07 16:08 ` dirk dot behme at googlemail dot com [this message]
2006-06-12 15:44 ` dirk dot behme at googlemail dot com
2006-06-26 19:13 ` rguenth at gcc dot gnu dot org
2006-07-15 19:22 ` enrico dot scholz at informatik dot tu-chemnitz dot de
2006-07-15 19:26 ` enrico dot scholz at informatik dot tu-chemnitz dot de
2006-07-18 21:42 ` pbrook at gcc dot gnu dot org
2006-07-20 13:57 ` pbrook at gcc dot gnu dot org
2006-07-20 13:59 ` pbrook at gcc dot gnu dot org
2006-07-20 15:07 ` pbrook at gcc dot gnu dot org
2006-07-20 15:08 ` pbrook at gcc dot gnu dot org
2006-07-20 15:37 ` rearnsha at gcc dot gnu dot org
2006-07-20 15:39 ` rearnsha at gcc dot gnu dot org
2006-07-22 6:21 ` yfw dot debian at gmail dot com
2006-07-22 6:24 ` dirk dot behme at googlemail dot com
2006-10-19 22:02 ` likewise at gmx dot net
2007-01-26 2:53 ` m dot k dot edwards 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=20060607155257.2942.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).