Can you GCC folks provide a macro to learn the code knows the name of input-charset, exec-charset and wide-exec-charset?

[unlvsur unlvsur via Gcc]

I desperately need to know exec-charset to do the correct codecvt.

Macros like __GNU_INPUT_CHARSET, __GNU_EXEC_CHARSET and __GNU_WIDE_EXEC_CHARSET 
would be great

Sent from Mail for Windows 10

Re: C++11 code in the gcc 10 branch

[Gerald Pfeifer]

On Mon, 21 Dec 2020, FX via Gcc wrote:
> I’m trying to bootstrap a GCC 10 compiler on macOS with clang, and I am 
> getting errors in stage 1, because there is C++11 code that is rejected 
> by clang (because the bootstrap involves compiling stage 1 with 
> -std=gnu++98, online on master (see top-level configure.ac).

I got reports from users, too (for FreeBSD with clang as system 
compiler), and have them test this patch which looks fine so far.

> These errors are not seen, I believe, when GCC is the bootstrap 
> compiler, because GCC will issue a warning instead of an error (as 
> clang does).
> 
> One place with such issue is in aarch64-builtins.c, which contains a 
> C++11 constructor. I can fix it with this:

When are you going to apply your fix that Richard S. approved on the
21st?

Gerald

Re: C++11 code in the gcc 10 branch

[FX via Gcc]

> When are you going to apply your fix that Richard S. approved on the
> 21st?

When I remember how to set up gcc’s git with write access, and remember how the 
new ChangeLog entries work. The times where I was a regular contributor were 
the CVS and SVN times.

I also wanted to ask approval to commit this diff below, fixing 
aarch64_get_extension_string_for_isa_flags()’s prototype to align it with the 
actual function definition:

diff --git a/gcc/config/aarch64/driver-aarch64.c 
b/gcc/config/aarch64/driver-aarch64.c
index 8840a2d9486c..d99834c99896 100644
--- a/gcc/config/aarch64/driver-aarch64.c
+++ b/gcc/config/aarch64/driver-aarch64.c
@@ -27,8 +27,7 @@
 #include "tm.h"
 
 /* Defined in common/config/aarch64/aarch64-common.c.  */
-std::string aarch64_get_extension_string_for_isa_flags (unsigned long,
-   unsigned long);
+std::string aarch64_get_extension_string_for_isa_flags (uint64_t, uint64_t);
 
 struct aarch64_arch_extension
 {


Although I admit that’s almost trivial (and it breaks build on aarch64-darwin), 
I’d prefer to be sure and ask. Then I’ll commit the two patches, if you think 
that’s OK.

FX

Re: C++11 code in the gcc 10 branch

[Richard Sandiford via Gcc]

FX  writes:
>> When are you going to apply your fix that Richard S. approved on the
>> 21st?
>
> When I remember how to set up gcc’s git with write access, and remember how 
> the new ChangeLog entries work. The times where I was a regular contributor 
> were the CVS and SVN times.
>
> I also wanted to ask approval to commit this diff below, fixing 
> aarch64_get_extension_string_for_isa_flags()’s prototype to align it with the 
> actual function definition:
>
> diff --git a/gcc/config/aarch64/driver-aarch64.c 
> b/gcc/config/aarch64/driver-aarch64.c
> index 8840a2d9486c..d99834c99896 100644
> --- a/gcc/config/aarch64/driver-aarch64.c
> +++ b/gcc/config/aarch64/driver-aarch64.c
> @@ -27,8 +27,7 @@
>  #include "tm.h"
>  
>  /* Defined in common/config/aarch64/aarch64-common.c.  */
> -std::string aarch64_get_extension_string_for_isa_flags (unsigned long,
> - unsigned long);
> +std::string aarch64_get_extension_string_for_isa_flags (uint64_t, uint64_t);
>  
>  struct aarch64_arch_extension
>  {

Yeah, that's OK everywhere it's needed, thanks.  (The other patch
was only needed on release branches.)

Richard

Re: C++11 code in the gcc 10 branch

[Iain Sandoe]

FX  wrote:


When are you going to apply your fix that Richard S. approved on the
21st?


When I remember how to set up gcc’s git with write access, and remember  
how the new ChangeLog entries work. The times where I was a regular  
contributor were the CVS and SVN times.


I also wanted to ask approval to commit this diff below, fixing  
aarch64_get_extension_string_for_isa_flags()’s prototype to align it with  
the actual function definition:


diff --git a/gcc/config/aarch64/driver-aarch64.c  
b/gcc/config/aarch64/driver-aarch64.c

index 8840a2d9486c..d99834c99896 100644
--- a/gcc/config/aarch64/driver-aarch64.c
+++ b/gcc/config/aarch64/driver-aarch64.c
@@ -27,8 +27,7 @@
#include "tm.h"

/* Defined in common/config/aarch64/aarch64-common.c.  */
-std::string aarch64_get_extension_string_for_isa_flags (unsigned long,
-   unsigned long);
+std::string aarch64_get_extension_string_for_isa_flags (uint64_t,  
uint64_t);


struct aarch64_arch_extension
{


Although I admit that’s almost trivial (and it breaks build on  
aarch64-darwin), I’d prefer to be sure and ask. Then I’ll commit the two  
patches, if you think that’s OK.


If Richard approves the second patch (and you’re stuck for time) - then  
send me the patch(es) as attachments with the commit credits you want, and  
I can apply them for you.


(thanks for the fixes)

cheers & happy new year all,

Iain

Re: C++11 code in the gcc 10 branch

[FX via Gcc]

> If Richard approves the second patch (and you’re stuck for time) - then send 
> me the patch(es) as attachments with the commit credits you want, and I can 
> apply them for you.

Both patches only needed on gcc-10, if you can commit that’s great, many thanks.

For credits in GCC I’m known as Francois-Xavier Coudert 
(and for the record, I do have a copyright assignment in place)

Happy new year to all,
FX

commit 96a9d0950453ca571b3999c2f4d4168da9d770f0
Author: Francois-Xavier Coudert 
Date:   2020-12-21 22:06:59 +0100

Fix prototype for aarch64_get_extension_string_for_isa_flags

Patch should be backported in gcc-10 branch

diff --git a/gcc/config/aarch64/driver-aarch64.c 
b/gcc/config/aarch64/driver-aarch64.c
index 8840a2d9486..d99834c9989 100644
--- a/gcc/config/aarch64/driver-aarch64.c
+++ b/gcc/config/aarch64/driver-aarch64.c
@@ -27,8 +27,7 @@
 #include "tm.h"
 
 /* Defined in common/config/aarch64/aarch64-common.c.  */
-std::string aarch64_get_extension_string_for_isa_flags (unsigned long,
-   unsigned long);
+std::string aarch64_get_extension_string_for_isa_flags (uint64_t, uint64_t);
 
 struct aarch64_arch_extension
 {
commit 3f1b98679eecdaf81ba5702a8de65bcb6b4ab25f
Author: Francois-Xavier Coudert 
Date:   2020-12-21 22:06:15 +0100

Remove C++11 constructor

Patch should be backported in gcc-10 branch

diff --git a/gcc/config/aarch64/aarch64-builtins.c 
b/gcc/config/aarch64/aarch64-builtins.c
index cba596765ac..184e9095d51 100644
--- a/gcc/config/aarch64/aarch64-builtins.c
+++ b/gcc/config/aarch64/aarch64-builtins.c
@@ -1225,8 +1225,9 @@ aarch64_init_memtag_builtins (void)
 = aarch64_general_add_builtin ("__builtin_aarch64_memtag_"#N, \
   T, AARCH64_MEMTAG_BUILTIN_##F); \
   aarch64_memtag_builtin_data[AARCH64_MEMTAG_BUILTIN_##F - \
- AARCH64_MEMTAG_BUILTIN_START - 1] = \
-   {T, CODE_FOR_##I};
+ AARCH64_MEMTAG_BUILTIN_START - 1].ftype = T; \
+  aarch64_memtag_builtin_data[AARCH64_MEMTAG_BUILTIN_##F - \
+ AARCH64_MEMTAG_BUILTIN_START - 1].icode = 
CODE_FOR_##I;
 
   fntype = build_function_type_list (ptr_type_node, ptr_type_node,
 uint64_type_node, NULL);

gcc-8-20201231 is now available

[GCC Administrator via Gcc]

Snapshot gcc-8-20201231 is now available on
  https://gcc.gnu.org/pub/gcc/snapshots/8-20201231/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 8 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch releases/gcc-8 
revision eb562189467626b3d8daa9bd734e444e07c9f38d

You'll find:

 gcc-8-20201231.tar.xzComplete GCC

  SHA256=01cea38ef6ad4f992e3e7d644e6c95a3c719880919df0be5574d859a1596c5b4
  SHA1=a710f3afe69f848b727e49a7c78a8dadd1b406c7

Diffs from 8-20201224 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-8
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.