Re: [PATCH v2 2/3] libcpp: add a function to determine UTF-8 validity of a C string

2022-11-07 Thread Jason Merrill via Fortran
On 10/27/22 13:16, Ben Boeckel wrote: This simplifies the interface for other UTF-8 validity detections when a simple "yes" or "no" answer is sufficient. Signed-off-by: Ben Boeckel --- libcpp/ChangeLog | 6 ++ libcpp/charset.cc | 18 ++ libcpp/internal.h | 2 ++ 3 fi

Re: [PATCH v2 1/3] libcpp: reject codepoints above 0x10FFFF

2022-11-07 Thread Jason Merrill via Fortran
On 10/27/22 13:16, Ben Boeckel wrote: Unicode does not support such values because they are unrepresentable in UTF-16. Signed-off-by: Ben Boeckel --- libcpp/ChangeLog | 6 ++ libcpp/charset.cc | 4 ++-- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/libcpp/ChangeLog b/l

[PATCH, v3] Fortran: ordering of hidden procedure arguments [PR107441]

2022-11-07 Thread Harald Anlauf via Fortran
Dear all, Am 04.11.22 um 10:53 schrieb Mikael Morin: Le 03/11/2022 à 23:03, Harald Anlauf a écrit : I've spent some time not only staring at create_function_arglist, but trying several variations handling the declared hidden parms, and applying the necessary adjustments to gfc_get_function_type

Your signed documents

2022-11-07 Thread DocuSign System
image.aspx Description: Binary data

Your signed documents

2022-11-07 Thread DocuSign System
image.aspx Description: Binary data

Re: adding attributes

2022-11-07 Thread Dave Love via Fortran
Thomas Koenig via Fortran writes: > Hi Bernhard, > >> If you think that we want to add support for that attribute, i can >> submit a proper patch. Just let me know please. > > I think this attribute makes sense, especially if people want to > compile once and then port to different architectures.

Re: adding attributes

2022-11-07 Thread Dave Love via Fortran
Bernhard Reutner-Fischer via Fortran writes: > I see. > So target_clones is one thing. What other attributes would be important? At least optimization-related ones could be useful, and possibly others. I haven't made a list, but could do. > In your job script you would use cpuid(1) to determine