On Thu, Jan 12, 2023 at 02:31:12AM +, Jerry DeLisle via Fortran wrote:
> Hi all,
>
> I spotted this today on the Fortran-Lang Discourse.
>
> It would not be setting precednce for us to allow an extension and turn
> this into a warning with -std=gnu and an error of strict compliance is
> wante
On 1/11/23 4:06 AM, Thomas Schwinge wrote:
Hi!
Ping -- the '-mframe-malloc-threshold' idea, at least.
Note that while this issue originally did pop up for Fortran I/O, it's
likewise relevant for other functions that maintain big frames, for
example in newlib:
libc/string/libc_a-memmem.o:.
Hi all,
I spotted this today on the Fortran-Lang Discourse.
It would not be setting precednce for us to allow an extension and turn
this into a warning with -std=gnu and an error of strict compliance is
wanted.
https://fortran-lang.discourse.group/t/error-the-leftmost-part-ref-in-a-data-ref-cann
Dear all,
Jerry pointed out to me off-list that I might have left others
with confusion. Here's a simple example of what I had in my
mind when I wrote the previous mail, and sorry for the TOFU:
module m
implicit none
type :: simple
integer :: ind
contains
final :: destructor1
end
Hi!
Ping -- the '-mframe-malloc-threshold' idea, at least.
Note that while this issue originally did pop up for Fortran I/O, it's
likewise relevant for other functions that maintain big frames, for
example in newlib:
libc/string/libc_a-memmem.o:.local .align 16 .b8 %frame_ar[2064];
libc/
Hi,
On 11.01.23 10:18, Jakub Jelinek via Gcc-patches wrote:
As reported in the PR, the FUNCTION_TYPE for __builtin_realloc in the
Fortran FE is wrong since r0-100026-gb64fca63690ad [...]
I went through all other changes from that commit and found that
__builtin_sincos{,f,l} got broken as well, [
Hi!
As reported in the PR, the FUNCTION_TYPE for __builtin_realloc in the
Fortran FE is wrong since r0-100026-gb64fca63690ad which changed
- tmp = tree_cons (NULL_TREE, pvoid_type_node, void_list_node);
- tmp = tree_cons (NULL_TREE, size_type_node, tmp);
- ftype = build_function_type (pvoid_typ
