From: David Edelsohn <dje@watson.ibm.com>
To: mod+linuxppc-dev@MissionCriticalLinux.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Link-time failures from "simple" CFLAGS changes
Date: Mon, 07 Jan 2002 17:10:45 -0500 [thread overview]
Message-ID: <200201072210.RAA09322@makai.watson.ibm.com> (raw)
In-Reply-To: Message from mod+linuxppc-dev@MissionCriticalLinux.com of "Mon, 07 Jan 2002 17:01:51 EST." <200201072201.RAA05808@missioncriticallinux.com>
>>>>> linuxppc-dev writes:
> When I change -O2 to -O0 in my CFLAGS definition in Makefile thus:
> CFLAGS := -g $(CPPFLAGS) -Wall -Wstrict-prototypes -Wno-trigraphs -O0 \
> -fno-strict-aliasing -fno-common
> CFLAGS := -g $(CPPFLAGS) -Wall -Wstrict-prototypes -Wno-trigraphs -O2 \
> -fno-strict-aliasing -fno-common
> ...I am astounded to see thousands of unresolved references
> at kernel link time. WTF? Any ideas?
GCC only inlines functions when optimizing and the Linux kernel
assumes inlining and other optimizations only present at -O2. The Linux
kernel requires optimization at least, and only really is tested at -O2.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-07 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 22:01 Link-time failures from "simple" CFLAGS changes mod+linuxppc-dev
2002-01-07 22:10 ` David Edelsohn [this message]
2002-01-07 22:15 ` Tom Rini
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=200201072210.RAA09322@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mod+linuxppc-dev@MissionCriticalLinux.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