Am 11.01.25 um 07:36 schrieb Steve Kargl:
> On Fri, Jan 10, 2025 at 05:19:34PM +, Paul Richard Thomas wrote:
>>
>> As of today, Gerhard Steinmetz has no fewer than 33 regressions to his name
>> out of a total of 54 for fortran and libgfortran. It's time that some of
>> these bugs are swatted, I
Am 12.01.25 um 19:33 schrieb Thomas Koenig:
> Hell world,
>
> after finding that an attribute I was looking for was not
> in the -fdump-fortran-original dump, I started putting in
> attributes and didn't stop until I had them all (or so
> I hope :-) It should be easier to read than looking at
> th
Hi Harald,
there is one irregularity here (partial lower case instead of
consistently upper case:
+ if (attr->oacc_declare_copyin)
+ fputs (" OACC-DECLARE-copyin", dumpfile);
Otherwise this is OK.
Thanks for catching this!
Committed with the fix as
r15-6840-gf4fa0b7d493a4ba217d989d3df75
Hi Thomas,
Am 12.01.25 um 19:33 schrieb Thomas Koenig:
Hell world,
after finding that an attribute I was looking for was not
in the -fdump-fortran-original dump, I started putting in
attributes and didn't stop until I had them all (or so
I hope :-) It should be easier to read than looking at
t
Hi Thomas,
Am 11.01.25 um 23:38 schrieb Thomas Koenig:
Hi Harald,
Thanks for pointing this out! I've also added a few gcc_unreachable()
to prevent other potential false positives, see attached.
Just a couple of documentation nits: The documentation says INTEGER
or REAL only, but it also wo
Hell world,
after finding that an attribute I was looking for was not
in the -fdump-fortran-original dump, I started putting in
attributes and didn't stop until I had them all (or so
I hope :-) It should be easier to read than looking at
the symbol attributes in a debugging session, and could
ho
Hello world,
I have committed the attached patch as obvious and simple after
regression-testing. I could not construct a test case that
actually failed, though, but the logic was wrong (pointer aliasing
and the field that was accessed had the wrong offset).
Commit is r15-6831-g40754a3b9bef83bf4
Am 11.01.25 um 18:32 schrieb Jerry D:
The attached patch is the latest clean build and test run I can come up
with. I completely cannot understand why moving the forall_iterator from
the sub-structure 'concur' back to where it was at the 'ext' sub-
structure of typedef struct gfc_code. 'ext' is