mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: GCC 3.4 and broken inlining.
Date: Fri, 09 Jul 2004 21:12:04 -0600	[thread overview]
Message-ID: <018101c4662b$ad61c830$6401a8c0@northbrook> (raw)
In-Reply-To: <fa.gktbdsg.1n4em8o@ifi.uio.no>

If you check the full gcc docs, the -Ox flags only enable omit-frame-pointer
on architectures where debugging is possible without a frame pointer. If you
use the actual -fomit-frame-pointer option, it is always omitted.

----- Original Message ----- 
From: "Pawel Sikora" <pluto@ds14.agh.edu.pl>
Newsgroups: fa.linux.kernel
To: "Michael Buesch" <mbuesch@freenet.de>
Cc: "linux kernel mailing list" <linux-kernel@vger.kernel.org>
Sent: Friday, July 09, 2004 4:25 AM
Subject: Re: GCC 3.4 and broken inlining.


> On Friday 09 of July 2004 11:43, Michael Buesch wrote:
> > Quoting Andi Kleen <ak@muc.de>:
> > > It's too bad that i386 doesn't enable -funit-at-a-time, that improves
> > > the inlining heuristics greatly.
> >
> > From the gcc manpage:
> >
> > -O2 turns on all optimization flags specified by -O. It
> > also turns on the following optimization flags: -fforce-mem
> > -foptimize-sibling-calls -fstrength-reduce -fcse-follow-jumps
> > -fcse-skip-blocks -frerun-cse-after-loop -frerun-loop-opt
> > -fgcse -fgcse-lm -fgcse-sm -fgcse-las -fdelete-null-pointer-checks
> > -fexpensive-optimizations -fregmove -fschedule-insns
> > -fschedule-insns2 -fsched-interblock -fsched-spec -fcaller-saves
> > -fpeephole2 -freorder-blocks -freorder-functions -fstrict-aliasing
> > -funit-at-a-time -falign-functions -falign-jumps -falign-loops
> > ^^^^^^^^^^^^^^^^
> > -falign-labels -fcrossjumping
> >
> > Do I miss something?
>
> # gcc-3.4.1/gcc/opts.c
>
>   if (optimize >= 2)
>     {
> (...)
>       flag_unit_at_a_time = 1;
>     }
>
> btw).
>
> I *don't trust* manpages ;)
>
> # man gcc
>
> -fomit-frame-pointer
>
>    Don't keep the frame pointer in a register for functions that don't
>    need one.  This avoids the instructions to save, set up and restore
>    frame pointers; it also makes an extra register available in many
>    functions.  It also makes debugging impossible on some machines.
>                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    (...)
>    Enabled at levels -O, -O2, -O3, -Os.
>    ^^^^^^^
>
>   if (optimize >= 1)
>     {
> (...)
> #ifdef CAN_DEBUG_WITHOUT_FP
>       flag_omit_frame_pointer = 1;
> #endif
> (...)
>
> finally, at ix86 -O[123s] doesn't turn on -fomit-frame-pointer.
> manpage tells somethine else...
>
> -- 
> /* Copyright (C) 2003, SCO, Inc. This is valuable Intellectual Property.
*/
>
>                            #define say(x) lie(x)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


       reply	other threads:[~2004-07-10  3:17 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.hnj36kg.4no2jk@ifi.uio.no>
     [not found] ` <fa.gktbdsg.1n4em8o@ifi.uio.no>
2004-07-10  3:12   ` Robert Hancock [this message]
     [not found] <2fVEt-6Vy-11@gated-at.bofh.it>
     [not found] ` <2fVO5-79H-3@gated-at.bofh.it>
     [not found]   ` <2fWqQ-7uv-19@gated-at.bofh.it>
     [not found]     ` <2g0b6-1Cf-23@gated-at.bofh.it>
2004-07-09 10:04       ` Andi Kleen
     [not found] <2fFzK-3Zz-23@gated-at.bofh.it>
     [not found] ` <2fG2F-4qK-3@gated-at.bofh.it>
     [not found]   ` <2fG2G-4qK-9@gated-at.bofh.it>
     [not found]     ` <2fPfF-2Dv-21@gated-at.bofh.it>
     [not found]       ` <2fPfF-2Dv-19@gated-at.bofh.it>
2004-07-09  4:51         ` Andi Kleen
2004-07-09  4:56           ` Nigel Cunningham
2004-07-09  5:46             ` Andi Kleen
2004-07-09  9:43               ` Michael Buesch
2004-07-09 10:23                 ` Paweł Sikora
2004-07-10 21:33             ` Alexandre Oliva
2004-07-11  5:52               ` Andi Kleen
2004-07-14  3:00                 ` Alexandre Oliva
2004-07-09 18:40           ` Adrian Bunk
2004-07-09 21:54             ` Andi Kleen
2004-07-09 22:17               ` Adrian Bunk
2004-07-10  4:50                 ` Andi Kleen
2004-07-10 21:25           ` Alexandre Oliva
2004-07-11  5:53             ` Andi Kleen
2004-07-11  6:55               ` Andrew Morton
2004-07-11  8:26                 ` Andi Kleen
2004-07-11  8:32                   ` Andrew Morton
2004-07-11  9:08                     ` Andi Kleen
2004-07-11 11:50                     ` Adrian Bunk
2004-07-11 13:01                       ` Arnd Bergmann
2004-07-08 11:46 Nigel Cunningham
2004-07-08 12:07 ` Jakub Jelinek
2004-07-08 12:11   ` Nigel Cunningham
     [not found]     ` <200407090036.39323.vda@port.imtp.ilyichevsk.odessa.ua>
2004-07-08 22:00       ` Nigel Cunningham
2004-07-08 22:41         ` Zan Lynx
2004-07-09  6:54           ` Arjan van de Ven
2004-07-10 21:20             ` Alexandre Oliva
2004-07-08 20:52   ` Adrian Bunk
2004-07-08 21:09     ` Arjan van de Ven
2004-07-08 22:08       ` Nigel Cunningham
2004-07-08 22:25         ` Adrian Bunk
2004-07-08 22:37           ` Nigel Cunningham
2004-07-09  6:24         ` Arjan van de Ven
2004-07-10  1:21           ` Adrian Bunk
2004-07-10  2:30             ` William Lee Irwin III
2004-07-13 22:19               ` Timothy Miller
2004-07-10  6:31             ` Arjan van de Ven
2004-07-10 21:17       ` Alexandre Oliva

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='018101c4662b$ad61c830$6401a8c0@northbrook' \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome