gcc-10-20210625 is now available

Snapshot gcc-10-20210625 is now available on https://gcc.gnu.org/pub/gcc/snapshots/10-20210625/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 10 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: __fp16 is ambiguous error in C++

> foo.c:6:23: error: call of overloaded 'exp(__fp16&)' is ambiguous __fp16 isn't ambiguous, calling std::exp with an argument of that type is ambiguous, because the standard library doesn't provide an overload for that type. It could be added (probably defined to cast to float and use the overloa

Re: Does GCC have __gnuc_literal_encoding__ macro defined?

GCC defines __GNUC_EXECUTION_CHARSET_NAME and __GNUC_WIDE_EXECUTION_CHARSET_NAME instead. https://gcc.gnu.org/onlinedocs/cpp/Common-Predefined-Macros.html#Common-Predefined-Macros

Re: __fp16 is ambiguous error in C++

On Thu, Jun 24, 2021 at 7:26 PM ALO via Gcc wrote: > foo.c: In function '__fp16 foo(__fp16, __fp16)': > foo.c:6:23: error: call of overloaded 'exp(__fp16&)' is ambiguous > 6 | return a + std::exp(b); > | ^ > No, there isn't a solution for this. You might want to try an ARM port clang/gcc to see

Re: replacing the backwards threader and more

On 6/25/21 10:20 AM, Aldy Hernandez via Gcc wrote: Hi folks. I'm done with benchmarking, testing and cleanups, so I'd like to post my patchset for review.  However, before doing so, I'd like to address a handful of meta-issues that may affect how I post these patches. Trapping on differences

Re: replacing the backwards threader and more

Hi folks. I'm done with benchmarking, testing and cleanups, so I'd like to post my patchset for review. However, before doing so, I'd like to address a handful of meta-issues that may affect how I post these patches. Trapping on differences === Originally I wanted to con

Re: daily report on extending static analyzer project [GSoC]

On Fri, 2021-06-25 at 20:33 +0530, Ankur Saini wrote: > AIM for today : > > - try to create an intra-procedural link between the calls the calling > and returning snodes > - figure out the program point where exploded graph would know about > the function calls > - figure out how the exploded nod

Re: daily report on extending static analyzer project [GSoC]

AIM for today : - try to create an intra-procedural link between the calls the calling and returning snodes - figure out the program point where exploded graph would know about the function calls - figure out how the exploded node will know which function to call - create enodes and eedges for

Does GCC have __gnuc_literal_encoding__ macro defined?

I just realized clang has this but clang does not support -fexec-charset. Clang Language Extensions — Clang 13 documentation (llvm.org) __clang_literal_encoding__ Defined to a narrow string literal that represents the current encoding of nar

Re: GCC documentation: porting to Sphinx

On 6/25/21 3:11 PM, Martin Liška wrote: List of known issues (planned to be fixed after merging): I forgot about: - diagnostics URL (for e.g. warnings) needs to be adjusted Martin

Re: GCC documentation: porting to Sphinx

Hello. I've got something that is very close to be a patch candidate that can be eventually merged. Right now, the patches are available here: https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=log;h=refs/users/marxin/heads/sphinx-v3 Changes since last version: - gdc manual was ported - 'make doc'

Re: replacing the backwards threader and more

On Fri, Jun 25, 2021 at 9:54 AM Richard Biener wrote: > > On Thu, Jun 24, 2021 at 6:14 PM Jeff Law wrote: > > > > > > > > On 6/21/2021 8:40 AM, Aldy Hernandez wrote: > > > > > > > > > On 6/9/21 2:09 PM, Richard Biener wrote: > > >> On Wed, Jun 9, 2021 at 1:50 PM Aldy Hernandez via Gcc > > >> wro

Re: replacing the backwards threader and more

On Thu, Jun 24, 2021 at 6:14 PM Jeff Law wrote: > > > > On 6/21/2021 8:40 AM, Aldy Hernandez wrote: > > > > > > On 6/9/21 2:09 PM, Richard Biener wrote: > >> On Wed, Jun 9, 2021 at 1:50 PM Aldy Hernandez via Gcc > >> wrote: > >>> > >>> Hi Jeff. Hi folks. > >>> > >>> What started as a foray into