From: Segher Boessenkool <segher@kernel.crashing.org>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Cc: tbsaunde+gcc@tbsaunde.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 0/9] start converting POINTER_SIZE to a hook
Date: Thu, 30 Jul 2015 04:55:00 -0000 [thread overview]
Message-ID: <20150730001438.GA28541@gate.crashing.org> (raw)
In-Reply-To: <55B8A808.3020303@foss.arm.com>
On Wed, Jul 29, 2015 at 11:16:40AM +0100, Richard Earnshaw wrote:
> I'm getting a bit worried about the potential performance impact from
> all these indirect function call hooks. This is a good example of when
> it's probably somewhat unnecessary. I doubt that the compiler could
> function correctly if this ever changed in the middle of a function.
It is also very ugly and much harder to read: it is longer, with more
useless interpunction, and there is nothing that makes clear it is a
constant.
Segher
next prev parent reply other threads:[~2015-07-30 0:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 3:10 tbsaunde+gcc
2015-07-27 3:10 ` [PATCH 9/9] emit-rtl.c: switch to targetm.pointer_size () tbsaunde+gcc
2015-07-27 3:10 ` [PATCH 2/9] add pointer_size target hook tbsaunde+gcc
2015-07-27 3:10 ` [PATCH 7/9] stor-layout.c: switch to targetm.pointer_size () tbsaunde+gcc
2015-07-27 3:10 ` [PATCH 4/9] varasm.c: switch from POINTER_SIZE " tbsaunde+gcc
2015-07-27 9:32 ` Richard Biener
2015-07-27 3:10 ` [PATCH 3/9] target.h: change to use targetm.pointer_size instead of POINTER_SIZE tbsaunde+gcc
2015-07-27 3:10 ` [PATCH 1/9] remove POINTER_SIZE_UNITS macro tbsaunde+gcc
2015-07-27 3:10 ` [PATCH 5/9] ubsan.c: switch from POINTER_SIZE to targetm.pointer_size () tbsaunde+gcc
2015-07-27 3:42 ` [PATCH 6/9] tree-chkp.c: switch " tbsaunde+gcc
2015-07-27 3:49 ` [PATCH 8/9] tree.c: " tbsaunde+gcc
2015-07-27 9:26 ` [PATCH 0/9] start converting POINTER_SIZE to a hook Richard Biener
2015-07-27 16:20 ` Jeff Law
2015-07-27 20:15 ` Richard Sandiford
2015-07-28 5:52 ` Trevor Saunders
2015-07-28 20:36 ` Richard Sandiford
2015-07-29 4:44 ` Trevor Saunders
2015-07-29 8:32 ` Richard Sandiford
2015-07-30 8:13 ` Trevor Saunders
2015-07-30 22:30 ` Richard Sandiford
2015-07-28 3:47 ` Trevor Saunders
2015-07-29 10:40 ` Richard Earnshaw
2015-07-30 4:55 ` Segher Boessenkool [this message]
2015-07-30 13:42 David Edelsohn
2015-07-30 22:26 ` Richard Sandiford
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=20150730001438.GA28541@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tbsaunde+gcc@tbsaunde.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).