On Wed, Jul 29, 2020 at 9:39 PM Gary Oblock wrote:
>
> Richard,
>
> Thanks, I had no idea about the immediate uses mechanism and
> using it will speed things up a bit and make them more reliable.
> However, I'll still have to scan the LHS of each assignment unless
> there's a mechanism to traverse
Richard,
Thanks, I had no idea about the immediate uses mechanism and
using it will speed things up a bit and make them more reliable.
However, I'll still have to scan the LHS of each assignment unless
there's a mechanism to traverse all the SSAs for a function.
Note, I assume there is also a mech
Hello Jakub,
Thank you very much for giving me a detailed instruction. I spent yesterday
studying the information over. I have few questions, and have also attached
a work-in-progress patch to confirm that I am heading the right direction.
On Tue, Jul 28, 2020 at 6:26 AM Jakub Jelinek wrote:
>
Hi.
Here I present the second report of the
"Automatic Detection of Parallel Compilation Viability" in Markdown
format.
---
# Automatic Parallel Compilation Viability: Second Report
## Complete Tasks
For the second evaluation,
On Fri, Jul 10, 2020 at 12:09 PM Nathan Sidwell wrote:
>
> On 7/9/20 3:28 PM, Fangrui Song via Gcc wrote:
> > Fix email addresses:)
> >
>
> IMHO the -f ones are misnamed.
> -fFOO -> affect generated code (non-target-specific) or language feature
> -gFOO -> affect debug info
> -mFOO -> machine-spec
On 7/28/20 2:57 PM, Andreas Schwab wrote:
On Jul 28 2020, William Seurer wrote:
There does not appear to be a check-gnat in any of the makefiles.
See LANG_MAKEFRAGS.
I see some stuff about that (and check-gnat, too) in some of the
makefile input files but it doesn't seem to do anything when
On Tue, Jul 28, 2020 at 11:02 PM Gary Oblock wrote:
>
> Richard,
>
> I wasn't aware of release_defs so I'll add that for certain.
>
> When I do a single transformation as part of the transformation pass
> each transformation uses the correct types internally but on the edges
> emits glue code that
