Hi,
On Thu, Jun 6, 2024 at 7:05 PM Andrew Pinski wrote:
>
> On Thu, Jun 6, 2024 at 9:00 AM David Malcolm wrote:
> >
> > On Thu, 2024-06-06 at 08:40 -0700, Andrew Pinski wrote:
> > > On Thu, Jun 6, 2024 at 6:02 AM Bert Wesarg
> > > wrote:
> > > >
Dear David,
On Tue, May 28, 2024 at 10:07 PM David Malcolm wrote:
>
> No functional change intended.
>
> Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
> Pushed to trunk as r15-874-g9bda2c4c81b668.
>
> libcpp/ChangeLog:
> * Makefile.in (TAGS_SOURCES): Add
David,
On Thu, Apr 9, 2015 at 10:29 AM, Bert Wesarg <bert.wes...@googlemail.com> wrote:
> Hi David,
>
>> Various tools that operate on source code files will inject markers
>> into them when an unfixable conflict occurs in a merger.
>>
>> There appears to be no
Hi,
better write your own instrumentation plug-in and do the filtering on
your own. The plug-in interface exists since 4.5 so you have a much
greater version base that can support your feature already, than some
future version of GCC which may have this patch. While we didn't
announced it here on
On Mon, Jun 1, 2015 at 11:04 PM, David Malcolm dmalc...@redhat.com wrote:
Provide a way to clean up state within the driver code, and use this
from libgccjit to embed it in-process, rather that via pex. Part of
this requires restoring the environment after any putenv calls, so the
patch
Hi David,
Various tools that operate on source code files will inject markers
into them when an unfixable conflict occurs in a merger.
There appears to be no blessed standard for these conflict markers,
but an ad-hoc convention is for 7 '' , '=', or '' characters at
the start of a line,
