Changes since v8:
* Documentation changes as requested by Sandra
* 3 functional test cases added
Torsten
gcc/c-family/ChangeLog
2017-06-13 Torsten Duwe
* c-attribs.c (c_common_attribute_table): Add entry for
"patchable_function_entry".
gcc/lto/ChangeLog
2017-06-
Richard, Ping?
On Tue, Jun 13, 2017 at 07:00:27PM +0200, Torsten Duwe wrote:
> Changes since v8:
>
> * Documentation changes as requested by Sandra
> * 3 functional test cases added
>
> Torsten
>
>
> gcc/c-family/ChangeLog
> 2017-06-13 Torsten Duwe
>
> * c-attribs.c (c_com
On 13/06/17 18:00, Torsten Duwe wrote:
> Changes since v8:
>
> * Documentation changes as requested by Sandra
> * 3 functional test cases added
>
> Torsten
>
>
> gcc/c-family/ChangeLog
> 2017-06-13 Torsten Duwe
>
> * c-attribs.c (c_common_attribute_table): Add entry for
>
On Tue, Jul 04, 2017 at 12:02:47PM +0100, Richard Earnshaw (lists) wrote:
> On 13/06/17 18:00, Torsten Duwe wrote:
> > Changes since v8:
> >
> > * Documentation changes as requested by Sandra
> > * 3 functional test cases added
> >
> > Torsten
> >
> >
> > gcc/c-family/ChangeLog
> > 2017
On 04/07/17 14:14, Torsten Duwe wrote:
> On Tue, Jul 04, 2017 at 12:02:47PM +0100, Richard Earnshaw (lists) wrote:
>> On 13/06/17 18:00, Torsten Duwe wrote:
>>> Changes since v8:
>>>
>>> * Documentation changes as requested by Sandra
>>> * 3 functional test cases added
>>>
>>> Torsten
>>>
>
Hello Richard,
On Tue, 4 Jul 2017, Richard Earnshaw (lists) wrote:
> > +void
> > +default_print_patchable_function_entry (FILE *file,
> > + unsigned HOST_WIDE_INT patch_area_size,
> > + bool record_p)
> > +{
> > + static const c
Hi,
On Tue, 4 Jul 2017, Michael Matz wrote:
> I don't think so: get_insn_template() should always return strings in
> .rodata, even for output statements, and should never point into GC
> memory.
Bah, ignore that. I should refetch mail before answering mid-thread ;)
Ciao,
Michael.
On Tue, Jul 04, 2017 at 02:27:00PM +0100, Richard Earnshaw (lists) wrote:
> >
> > How about omitting the recording step and document that? This way the
> > instrumentation can still be useful on e.g. a.out format; the framework
> > would then have to check around each function entry whether the NO
