Thanks, for confirming David. I think it was too big in the end. I was
trying to figure out how to actually split that up but it seems
reasonable that I can split up the front-end patches into patches for
each separate pass in the compiler seems like a reasonable approach
for now.
--Phil
On Wed,
Hi Thomas,
I think you are right here. There are parts in
libstd/liballoc/libpanic which start to look for what CPU features are
available iirc. Maintaining our patches here has been becoming
difficult as of late, especially when it comes to libcore, which just
cares about target pointer width and
Schwinge wrote:
>
> Hi Phil!
>
> On 2022-07-28T11:51:37+0100, Philip Herron wrote:
> > I think you are right here. There are parts in
> > libstd/liballoc/libpanic which start to look for what CPU features are
> > available iirc.
>
> Aha, good. That -- once we
x27;t build.
I hope this makes sense.
Thanks
--Phil
On Thu, 28 Jul 2022 at 10:39, Philip Herron wrote:
>
> Thanks, for confirming David. I think it was too big in the end. I was
> trying to figure out how to actually split that up but it seems
> reasonable that I can split up the fro
In development of the Rust FE logging is useful in debugging. Instead of
rolling our own logger it became clear the loggers part of analyzer and jit
projects could be extracted and made generic so they could be reused in
other projects.
To test this patch make check-jit was invoked, for analyzer t
On 04/03/2021 16:45, David Malcolm wrote:
> On Thu, 2021-03-04 at 16:17 +0000, Philip Herron wrote:
>> In development of the Rust FE logging is useful in debugging. Instead
>> of
>> rolling our own logger it became clear the loggers part of analyzer
>> and jit
>>
On 05/03/2021 14:18, David Malcolm wrote:
> On Fri, 2021-03-05 at 10:58 +0000, Philip Herron wrote:
>> On 04/03/2021 16:45, David Malcolm wrote:
>>> On Thu, 2021-03-04 at 16:17 +0000, Philip Herron wrote:
>>>> In development of the Rust FE logging is useful in d
the following
flags were used -fanalyzer -fdump-analyzer -fanalyzer-verbosity=4.
gcc/ChangeLog:
2021-03-8 Philip Herron
* logging.h: added new generic logger based off analyzer's logger
* logging.c: Likewise
gcc/analyzer/ChangeLog:
2021-03-8 Philip Herron
* ana
Hi Martin,
Not right now, it is on the to-do list, but do we have to do it in texinfo?
Thanks
--Phil
On Wed, 24 Aug 2022 at 14:49, Martin Liška wrote:
>
> On 8/15/22 16:33, Martin Liška wrote:
> > On 8/15/22 16:07, Manuel López-Ibáñez via Gcc-patches wrote:
> >> Dear Philip,
> >>
> >> Another
Hi everyone
I noticed a few patches still didn't make it through here with the
400kb limit. In the meantime, Mark pointed out to me that they can all
be viewed over here:
https://inbox.sourceware.org/gcc-patches/20220824115956.737931-9-philip.her...@embecosm.com/T/#rbff0bb3df2780fecd9ee3d2baa864d
-logo.patch
I hope this helps. I can do another pass at splitting up on these
patches if it will help.
--Phil
On Thu, 25 Aug 2022 at 10:52, Martin Liška wrote:
>
> On 8/25/22 11:46, Philip Herron wrote:
> > The missing patches on
> > https://gcc.gnu.org/pipermail/gcc-patches/2022-
On Thu, 25 Aug 2022 at 13:50, Frank Ch. Eigler wrote:
>
> Hi -
>
>
> > 12K 0004-gccrs-Add-link-cases-testsuite.patch
> > 356K0005-gccrs-Add-general-compilation-test-cases.patch
> > 132K0006-gccrs-Add-execution-test-cases.patch
> > 4.0K0007-gccrs-Add-gcc-check-target-check-rust.patc
Added install hook:
/opt/gjit/bin/gcc -g -O2 -Wall t.c -o test -I/opt/gjit/include
-lgccjit -L/opt/gjit/lib
Compiles the helloworld examples correctly and it runs instead of
pointing to my gcc build dir. Am working on getting more involved with
this and started:
https://github.com/redbrain/spy
On 12 February 2014 00:52, David Malcolm wrote:
> On Tue, 2014-02-11 at 16:51 +0000, Philip Herron wrote:
> [adding the j...@gcc.gnu.org ML to the CC]
>
>> Added install hook:
>
> Thanks!
>
> I don't know that this is needed for a 3-line patch, but have you
14 matches
Mail list logo
