Re: [GSoC] Conflicted Built-in Trait Name

On Sat, Mar 25, 2023 at 5:38 AM Marc Glisse wrote: > > On Sat, 25 Mar 2023, Ken Matsui via Gcc wrote: > > > Built-in trait naming simply adds two underscores (__) to the original > > trait name. However, the same names are already in use for some > > built-in traits, such as is_void, is_pointer, a

Re: Building gcc-12 on MacOS Ventura (aarch64)

On 25/3/2023 11:08 am, Stuff Received wrote: > On 2023-03-24 19:51, Chris Johns wrote: >> On 25/3/2023 10:07 am, Jonathan Wakely wrote: >>> On Fri, 24 Mar 2023, 23:07 Jonathan Wakely, >> > wrote: >>> On Fri, 24 Mar 2023, 23:03 Chris Johns, >>

gcc-12-20230325 is now available

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

[GSoC] Interest and initial proposal for project on reimplementing cpychecker as -fanalyzer plugin

Hi GCC community, For GSoC, I am extremely interested in working on the selected project idea with respect to extending the static analysis pass. In particular, porting gcc-python-plugin's cpychecker to a plugin for GCC -fanalyzer as described in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107646

Re: Website https://gcc.gnu.org/ down

Hi Damian, On Sat, Mar 25, 2023 at 07:30:14AM +0100, Damian Tometzki wrote: > the website and git https://gcc.gnu.org/ is down ? > > Any info about it ? The site isn't down, but there is an issue (ddos?) with the fsf dns servers for gnu.org. The FSF tech team announces downtime and temporary iss

Re: The macro STACK_BOUNDARY may overflow

On 3/24/23 07:48, Paul Iannetta via Gcc wrote: Hi, Currently, the macro STACK_BOUNDARY is defined as Macro: STACK_BOUNDARY Define this macro to the minimum alignment enforced by hardware for the stack pointer on this machine. The definition is a C expression for the des

Website https://gcc.gnu.org/ down

Hello together, the website and git https://gcc.gnu.org/ is down ? Any info about it ? best regards Damian

Re: [GSoC] Conflicted Built-in Trait Name

On Sat, 25 Mar 2023, Ken Matsui via Gcc wrote: Built-in trait naming simply adds two underscores (__) to the original trait name. However, the same names are already in use for some built-in traits, such as is_void, is_pointer, and is_signed. For example, __is_void is used in the following file

Re: [GSoC] Conflicted Built-in Trait Name

Clang has been providing __is_void for a very long time now, and is definitely compatible with libstdc++. Does defining this builtin cause a problem? Might be that the lookup rules for builtins are different or something. https://clang.llvm.org/docs/LanguageExtensions.html#type-trait-primitives O

[GSoC] Conflicted Built-in Trait Name

Hi, I am working on the GSoC project, "C++: Implement compiler built-in traits for the standard library traits". Built-in trait naming simply adds two underscores (__) to the original trait name. However, the same names are already in use for some built-in traits, such as is_void, is_pointer, and