From: kevin diggs <diggskevin38@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: hail marry (booting PowerMac 8600)
Date: Wed, 02 Feb 2011 22:23:00 -0000 [thread overview]
Message-ID: <AANLkTi=hcLj3jfLnFkTwXrE5RN+O9888eOtzRUOTzxG8@mail.gmail.com> (raw)
In-Reply-To: <mcroc6udrac.fsf@google.com>
Hi,
The differences are pretty extensive. But I will try to weed through
it and see if something jumps out.
According to the .mesh.o.cmd file -fno-strict-overflow is also there.
If it helps, I don't think 4.2.4 works either. I have not repeated the
exact test (a 4.2.4 compiled mesh with 4.3.5 everything else) but I
have tried to build the entire kernel with 4.2.4 and it behaved the
same as 4.3.5. Any chance the list of changes is smaller (between
4.1.2 and 4.2.4)?
Thanks!
kevin
On Wed, Feb 2, 2011 at 4:07 PM, Ian Lance Taylor <iant@google.com> wrote:
>
> Many many things changed. I would recommend looking at the code
> generated by the two compilers to see if you can spot the key
> difference.
>
> As a short in the dark, you said you use -fno-strict-aliasing; do you
> also use -fno-strict-overflow?
>
> Ian
>
cmd_drivers/scsi/mesh.o := gcc -m32 -Wp,-MD,drivers/scsi/.mesh.o.d \
-nostdinc -isystem
/opt/gcc-4.3.5-gnu/lib/gcc/powerpc-unknown-linux-gnu/4.3.5/include \
-I/mnt/mnt3/linux-2.6.36/arch/powerpc/include -Iinclude \
-include include/generated/autoconf.h -D__KERNEL__ \
-Iarch/powerpc -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
-fno-strict-aliasing -fno-common -Werror-implicit-function-declaration \
-Wno-format-security -fno-delete-null-pointer-checks -O2 -msoft-float \
-pipe -Iarch/powerpc -ffixed-r2 -mmultiple -mno-altivec -mno-spe -mspe=no \
-funit-at-a-time -mno-string -mcpu=powerpc -Wa,-maltivec -fno-stack-protector \
-fomit-frame-pointer -Wdeclaration-after-statement -Wno-pointer-sign \
-fno-strict-overflow -D"KBUILD_STR(s)=\#s" \
-D"KBUILD_BASENAME=KBUILD_STR(mesh)" \
-D"KBUILD_MODNAME=KBUILD_STR(mesh)" -c \
-o drivers/scsi/mesh.o drivers/scsi/mesh.c
next prev parent reply other threads:[~2011-02-02 22:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 2:10 kevin diggs
2011-01-22 2:36 ` Ian Lance Taylor
2011-01-25 4:16 ` kevin diggs
2011-02-02 19:41 ` kevin diggs
2011-02-02 20:04 ` Jeff Kenton
2011-02-02 21:06 ` kevin diggs
2011-02-02 22:07 ` Ian Lance Taylor
2011-02-02 22:23 ` kevin diggs [this message]
2011-02-02 22:36 ` Ian Lance Taylor
2011-02-03 0:03 ` kevin diggs
2011-02-03 0:13 ` Ian Lance Taylor
2011-02-03 0:59 ` kevin diggs
2011-02-03 1:58 ` Ian Lance Taylor
2011-02-03 8:39 ` VAUGHAN Jay
2011-02-03 21:10 ` kevin diggs
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='AANLkTi=hcLj3jfLnFkTwXrE5RN+O9888eOtzRUOTzxG8@mail.gmail.com' \
--to=diggskevin38@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
/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).