Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] Compiler switches
Date: Sun, 2 Feb 2003 03:59:20 +0000	[thread overview]
Message-ID: <20030202035920.F21040@parcelfarce.linux.theplanet.co.uk> (raw)

Just wondering how many of the compiler switches we really need these days.
Here's what we currently do:

cflags-y        := -D__linux__ -pipe -fno-strength-reduce

# These should be on for older toolchains or SOM toolchains that don't
# enable them by default.
cflags-y        += -mno-space-regs -mfast-indirect-calls

# No fixed-point multiply
cflags-y        += -mdisable-fpregs

# Without this, "ld -r" results in .text sections that are too big
# (> 0x40000) for branches to reach stubs.
cflags-y        += -ffunction-sections


-D__linux__ looks like it can go away.

-pipe I'm agnostic on.  Someone want to benchmark builds both with and
without it?

-fno-strength-reduce has been there since before we moved to ELF -- over 3
years.  Any bug this was working around has hopefully been long-squashed.
I think we should eliminate this and submit PRs if it finds new holes.

-mno-space-regs & -mfast-indirect-calls can also go away, I think.
I can't imagine that we ever didn't have them as default on a gcc
3.0-based compiler.

Do we still need -ffunction-sections?  I'm inclined to leave it anyway
to enable compilation with older toolchains.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

             reply	other threads:[~2003-02-02  3:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02  3:59 Matthew Wilcox [this message]
2003-02-02  4:56 ` [parisc-linux] Compiler switches John David Anglin
2003-02-02  5:19   ` Randolph Chung
2003-02-02  5:49     ` John David Anglin
2003-02-02  5:52     ` John David Anglin
2003-02-02  5:55       ` John David Anglin
2003-02-02  8:18       ` Randolph Chung
2003-02-02 21:03   ` Matthew Wilcox
2003-02-02 22:02     ` John David Anglin
2003-02-06 22:21       ` John David Anglin

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=20030202035920.F21040@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=parisc-linux@parisc-linux.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