From: "Richard Biener via gcc" <gcc@gcc.gnu.org>
To: sellcey@cavium.com
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Question about dump_printf/dump_printf_loc
Date: Mon, 08 May 2017 07:09:00 -0000 [thread overview]
Message-ID: <CAFiYyc2Zd3wH4bAMfDjp5fgKBPB=Qo5DiunRiW6-rnAqXng8Og@mail.gmail.com> (raw)
In-Reply-To: <201705052237.v45Mbq6G008507@sellcey-dt.caveonetworks.com>
On Sat, May 6, 2017 at 12:37 AM, Steve Ellcey <sellcey@cavium.com> wrote:
> I have a simple question about dump_printf and dump_printf_loc. I notice
> that most (all?) of the uses of these function are of the form:
>
> if (dump_enabled_p ())
> dump_printf_loc (MSG_*, ......);
>
> Since dump_enabled_p() is just checking to see if dump_file or alt_dump_file
> is set and since dump_printf_loc has checks for these as well, is there
> any reason why we shouldn't or couldn't just use:
>
> dump_printf_loc (MSG_*, ......);
>
> with out the call to dump_enabled_p and have the dump function do nothing
> when there is no dump file set? I suppose the first version would have
> some performance advantage since dump_enabled_p is an inlined function,
> but is that enough of a reason to do it? The second version seems like
> it would look cleaner in the code where we are making these calls.
The purpose of dump_enabled_p () is to save compile-time for the common case,
esp. when guarding multiple dump_* calls. But also for the single-called case.
You could try improve things by having inline wrappers for all dump_* cases that
inline a dump_enabled_p () call but that would be somewhat gross.
Richard.
> Steve Ellcey
> sellcey@cavium.com
next prev parent reply other threads:[~2017-05-08 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 22:37 Steve Ellcey
2017-05-08 7:09 ` Richard Biener via gcc [this message]
2017-05-08 22:12 ` 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='CAFiYyc2Zd3wH4bAMfDjp5fgKBPB=Qo5DiunRiW6-rnAqXng8Og@mail.gmail.com' \
--to=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=sellcey@cavium.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).