Hi Guys,
OK, so playing the devils advocate here...
> Mostly I just want the compiler people to say they'll guarantee the
> behaviour if we do 'X'. If 'X' happens to be 'any dynamic branch headed
> by a volatile load' that's fine by me.
Is a compiler hack really the right way to go here ?
Hi Guys,
>> linux-toolcha...@vger.kernel.org
> Created.
I have been able to subscribe to this list, so it looks like thunderbirds are
go...
Cheers
Nick
Hi Guys,
>> so when I take empty object and compile like:
>>
>> $ echo 'int main(int argc, char **argv) { return 0; }' | gcc -c -o ex.o -g
>> -gz=zlib -x c -
>> $ ld -o ex --compress-debug-sections=zlib ex.o
Thanks Mark. I have now created a binutils PR for this bug, and I am looking
into
Hi Mark,
> Adding Nick, the binutils maintainer, so we can make sure
> binutils/elfutils agree on some ELF section compression corner case.
Thanks for doing this.
> But it would obviously be better if that wasn't necessary. So I'll try
> to fix libelf so that if it fixes up the alignment when re
Hi Nick,
> + Nick, H.J.
> I'm unfamiliar with the git tag conventions of binutils. Does a patch
> that landed in 2.25.51.0.4 mean it shipped in the official 2.25
> release, or 2.26 release? Specifically, commit 19a7fe52ae3d.
2.26.
The convention is that a released form of the binutils has a ve
Hi Arnaldo,
[oops- hit send by mistake...]
>> Sorry - I do not think that I have the authority to do that. I am not a
> Ok, I was more thinking about this part of
> Documentation/process/submittingpatches.txt:
>
>
> Acked-by: is not as formal as Signed-off-by:.
Hi Arnaldo,
>> Sorry - I do not think that I have the authority to do that. I am not a
>> perftools maintainer (or a kernel maintainer). For what it is worth the
>> patch does look good to me, but I think that a real maintainer needs to
>> approve it.
>
> Ok, I was more thinking about this pa
Hi Arnaldo,
>> there were no objections for rfc, sending patch
>
> I don't see a problem, Nick, can you provide an Acked-by, or better yet,
> a Reviewed-by so that Jiri can collect in this patch and I can push it
> to perf/urgent?
Sorry - I do not think that I have the authority to do that. I a
Hi Arnaldo,
>>> Humm, is -fno-omit-frame-pointer there by any chance? :-)
> Would be interestint to have that info, as we could hint the user that
> backtraces should be done with something else than '--call-graph fp' :-)
OK, well I have added the feature to annobin 8.67, now in Fedora
rawhide.
Hi Arnaldo,
>> Unfortunately the annobin notes will probably not be very helpful as they
>> only record a minor subset of the typical gcc command line options.
>> (Specifically: -O, -g, -D_FORTIFY_SOURCE, -D_GLIBCXX_ASSERTIONS,
>> -fcf-protection, -fpic (and variants), -fshort-enum,
>> -fstack-c
Hi Guys,
>> Humm, it would be nice for perf annotate to show those options when one
>> navigates the annotation,
Usually the command line options can also be found in the debug info for
the executable. Assuming it has not been stripped, of course.
One of the advantages of the annobin strategy
Hi Jiri,
> When perf is built with annobin plugin (RHEL8 build) extra symbols
> are added to its binary:
A bit of background for those wondering why annobin is creating
these symbols: Annobin is a plugin for gcc that records data
about how object file were built. It is specifically desig
Hi Laura,
> This is an implementation of the counter proposal. If an environment variable
> is set, that value gets added as a .comment section to the necessary binaries.
This is not really my purview but ... can I just say that I really do not like
using environment variables to control build be
Hi Adrian,
What are the plans regarding getting a plain upstream gcc compiling the
kernel?
One of the things on my plate is to get the -mno-mem-funcs patch
contributed upstream. (Along with a lot of other pending AM33 patches,
such as the support for the AM34 processor). As it happens MEI
Hi RAM,
The following result was the effect of "info threads"
command
Since this is GDB bug that you are reporting, please could you either
send it to the GDB mailing list at <[EMAIL PROTECTED]> or else fill in
a bug report at:
http://sourceware.org/gdb/bugs/
Thank you.
Nick
-
To unsub
15 matches
Mail list logo
