Am 18.02.25 um 16:00 schrieb Andre Vehreschild:
Hi Thomas,
This patch series (of necessity) introduces ABI changes. What will
happen with user code compiled against the old interface?
That depends on the library you are linking against. When using caf_single from
gfortran, then you will get
I am trying to compile some C and fortran code inserted into a dll to be
called by Excel. However, on each successful Fortran open statment Excel
crashes without any message. Everything else works perfectly so I am
sure the Excel/DLL interface works in principle.
I also found out, that the crash
With a compiler setup to compile (also) for nvptx offloading,
the testcase triggered a bogus error - and that prevents in
addition the gimple scan.
Fixed by adding an xfail and an xfailed dg-bogus.
The issue itself is the known https://gcc.gnu.org/PR118694
Committed as obvious asr15-7606-g8d922
Hi Jerry,
thank you very much for taking on the job of reviewing and sorry for my late
answer. In fact, I was having a hard time figuring regressions in the
OpenCoarrays library.
This also answers your first question: Yes, OpenCoarrays will make use of the
new interface. Most of the changes in th
Hi Thomas,
> This patch series (of necessity) introduces ABI changes. What will
> happen with user code compiled against the old interface?
That depends on the library you are linking against. When using caf_single from
gfortran, then you will get link failures when you mix code compiled by
gfor
