From: James Bowman <james.bowman@ftdichip.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH, FT32] initial support
Date: Wed, 11 Feb 2015 23:58:00 -0000 [thread overview]
Message-ID: <CA9BBF0458F83C4F9051448B941B57D11716AFEC@glaexch1> (raw)
In-Reply-To: <alpine.DEB.2.10.1502111702190.24912@digraph.polyomino.org.uk>
> > +@table @gcctabopt
> > +
> > +@item -mspace
> > +@opindex mspace
> > +Enable code-size optimizations.
> > +Some of these optimizations incur a minor performance penalty.
>
> We already have -Os, so why is an architecture-specific option for this
> needed?
Code compiled with -mspace is somewhat slower than code without.
So we typically build *all* code with -Os, with everything
non-critical also compiled -mspace.
Is this a legitimate option or should I just use -Os?
--
James Bowman
FTDI Open Source Liaison
next prev parent reply other threads:[~2015-02-11 23:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 5:18 James Bowman
2015-02-03 6:05 ` Andrew Pinski
2015-02-03 14:44 ` Paolo Bonzini
2015-02-04 2:26 ` James Bowman
2015-02-03 22:51 ` Joseph Myers
2015-02-11 3:42 ` James Bowman
2015-02-11 17:04 ` Joseph Myers
2015-02-11 23:58 ` James Bowman [this message]
2015-02-12 12:39 ` Joseph Myers
2015-02-16 10:00 ` James Bowman
2015-02-16 18:07 ` Joseph Myers
2015-02-16 22:36 ` James Bowman
2015-03-10 15:49 ` James Bowman
2015-03-19 15:29 ` James Bowman
2015-04-29 7:41 ` Jeff Law
[not found] ` <CA9BBF0458F83C4F9051448B941B57D117B98521@glaexch3>
2015-05-11 20:35 ` Jeff Law
2015-05-12 22:36 ` James Bowman
2015-05-12 22:54 ` Jeff Law
2015-05-12 23:10 ` Mike Stump
2015-05-13 1:07 ` Segher Boessenkool
2015-05-14 1:58 ` James Bowman
2015-05-14 11:40 ` Segher Boessenkool
2015-05-14 12:58 ` Segher Boessenkool
2015-05-14 13:11 ` Segher Boessenkool
2015-05-14 15:30 ` James Bowman
2015-05-14 17:42 ` Segher Boessenkool
2015-05-14 18:48 ` Jeff Law
2015-05-14 19:51 ` Segher Boessenkool
2015-05-14 20:06 ` Jeff Law
2015-05-15 3:01 ` James Bowman
2015-05-15 6:41 ` Jeff Law
2015-05-28 22:35 ` Eric Botcazou
2015-06-03 13:56 ` Jeff Law
2015-05-14 18:31 ` Jeff Law
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=CA9BBF0458F83C4F9051448B941B57D11716AFEC@glaexch1 \
--to=james.bowman@ftdichip.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).