From: Sriraman Tallam <tmsriram@google.com>
To: Jeff Law <law@redhat.com>
Cc: Ian Lance Taylor <iant@google.com>, David Li <davidxl@google.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Using -ffunction-sections and -p
Date: Tue, 04 Dec 2012 21:43:00 -0000 [thread overview]
Message-ID: <CAAs8Hmz5_dHAHZnMosiyd0bsZ_k8mWGuvua-ru0x0-TFmhGBsQ@mail.gmail.com> (raw)
In-Reply-To: <50BE6B98.80908@redhat.com>
On Tue, Dec 4, 2012 at 1:31 PM, Jeff Law <law@redhat.com> wrote:
> On 12/03/2012 01:08 PM, Sriraman Tallam wrote:
>>
>> Hi Jeff,
>>
>> Wondering if you got a chance to do this?
>
> Hmm, thinking more about this, it couldn't have been a 32 bit HPUX issue.
> First that port claims to not support -ffunction-sections -- which is true,
> we can't make arbitrarily named sections, though each function is placed
> into its own $CODE$ section/subspace.
>
> Second, even with each function in its own $CODE$ subspace, profiling works.
>
> So it couldn't have been 32 bit HPUX.
>
> I think Ian's plan of going forward and see if anyone complains is
> reasonable. Regardless, we're talking about OSs that are > 10 years old,.
> the odds of folks building modern versions of GCC is pretty slim. The odds
> they're building modern versions of GCC and care about both
> function-sections and profiling is probably approaching zero.
>
> Jeff
>
next prev parent reply other threads:[~2012-12-04 21:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 4:04 Sriraman Tallam
2012-11-05 5:03 ` Ian Lance Taylor
2012-11-14 18:58 ` Sriraman Tallam
2012-11-14 20:01 ` Ian Lance Taylor
2012-11-14 20:04 ` Jeff Law
2012-11-14 20:32 ` Ian Lance Taylor
2012-11-14 22:41 ` Jeff Law
[not found] ` <CAAs8HmzV1g0GHiGgaUnBE4fDGLyxk31JirrxFOJnZLoOPW_aUg@mail.gmail.com>
[not found] ` <50BE6B98.80908@redhat.com>
2012-12-04 21:43 ` Sriraman Tallam [this message]
2012-12-07 22:46 ` Sriraman Tallam
2012-12-07 22:47 ` 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=CAAs8Hmz5_dHAHZnMosiyd0bsZ_k8mWGuvua-ru0x0-TFmhGBsQ@mail.gmail.com \
--to=tmsriram@google.com \
--cc=davidxl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=law@redhat.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).