Snapshot gcc-10-20221215 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20221215/
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
Hi Martin,
On 12/15/22 21:50, Martin Sebor wrote:
On 12/14/22 16:14, Alejandro Colomar via Libc-alpha wrote:
[...]
int
main(void)
{
char buf[BUFSIZ];
size_t len;
buf[0] = '\0'; // There’s no ’cpy’ function to
Sorry, I just saw that I only answered Jakub and Tobias directly instead of
CCing the List,
so I will just forward my answer to Tobias to avoid wasting anyones time.
Original Message
Subject: Re: GOMP: OMP 5.1: simd construct for non-pointer random access
iterators
Date: Th
Hi,
On 15.12.22 21:31, Grosse-Bley, Paul Leonard wrote:
I just ran into the issue that `#pragma omp simd` does not work on C++ iterator
loops (godbolt).
From going through the specifications I understand that this restriction was
part of 4.5 and 5.0, but was dropped with 5.1.
I assume that i
On 12/14/22 16:14, Alejandro Colomar via Libc-alpha wrote:
[CC += groff]
Hi Andrew,
On 12/14/22 23:57, Andrew Pinski wrote:
On Wed, Dec 14, 2022 at 2:46 PM Alejandro Colomar via Libc-alpha
wrote:
Hi,
I was rewriting the strncat(3) manual page, and when I tried to
compile the
example prog
On Thu, Dec 15, 2022 at 09:31:50PM +0100, Grosse-Bley, Paul Leonard wrote:
>
> Hi together,
>
> I just ran into the issue that `#pragma omp simd` does not work on C++
> iterator loops (godbolt).
> >From going through the specifications I understand that this restriction was
> >part of 4.5 and 5
Hi together,
I just ran into the issue that `#pragma omp simd` does not work on C++ iterator
loops (godbolt).
>From going through the specifications I understand that this restriction was
>part of 4.5 and 5.0, but was dropped with 5.1.
As I couldn't find this change in the table of 5.1 (or 5.2
On Thu, 15 Dec 2022, 20:04 Jonathan Wakely, wrote:
>
>
> On Thu, 15 Dec 2022, 19:50 U.Mutlu, wrote:
>
>> Jakub Jelinek wrote on 12/15/22 17:59:
>> > On Thu, Dec 15, 2022 at 05:53:19PM +0100, U.Mutlu wrote:
>> >> On this page all ISO C++ standards versions of gcc/g++ are listed,
>> except C++03:
On Thu, 15 Dec 2022, 19:50 U.Mutlu, wrote:
> Jakub Jelinek wrote on 12/15/22 17:59:
> > On Thu, Dec 15, 2022 at 05:53:19PM +0100, U.Mutlu wrote:
> >> On this page all ISO C++ standards versions of gcc/g++ are listed,
> except C++03:
> >> https://gcc.gnu.org/projects/cxx-status.html
> >>
> >> This
Jakub Jelinek wrote on 12/15/22 17:59:
On Thu, Dec 15, 2022 at 05:53:19PM +0100, U.Mutlu wrote:
On this page all ISO C++ standards versions of gcc/g++ are listed, except C++03:
https://gcc.gnu.org/projects/cxx-status.html
This looks much like an error/omission b/c g++ has the options -std=c++03
What is going on out there these days? I've added more addresses from
the GCC mailing list to my killfile in the last week than in the
previous two years combined.
Yeesh.
On Thu, Dec 15, 2022 at 05:53:19PM +0100, U.Mutlu wrote:
> On this page all ISO C++ standards versions of gcc/g++ are listed, except
> C++03:
> https://gcc.gnu.org/projects/cxx-status.html
>
> This looks much like an error/omission b/c g++ has the options -std=c++03
> and -std=gnu++03
C++03 isn'
On this page all ISO C++ standards versions of gcc/g++ are listed, except C++03:
https://gcc.gnu.org/projects/cxx-status.html
This looks much like an error/omission b/c g++ has the options -std=c++03 and
-std=gnu++03
On Wed, 2022-12-14 at 17:32 +0200, Mohamed Atef via Gcc wrote:
> Hello all,
> As I mentioned before, I don't have much time to contribute.
> So is there any way I can contribute some medium project I can work
> on but myself in the long run? I loved this community, I contributed
> before so can
Ok.
And as you point out it is redundant code rather than dead code, to be
precise.
On Wed, Dec 14, 2022, 1:47 PM Richard Biener
wrote:
>
>
> > Am 14.12.2022 um 18:28 schrieb G.T. via Gcc :
> >
> > At line 276, lra_assert (spill_class != NO_REGS); would trigger
> > whenever execution reached h
Dear Team GCC GNU ORG,
please assist me with getting the assembler language reference
the GCC implementation is based on lately
Thank you and
Have a great day
Jeannot Deumer
Hi, thanks for your interest.
There are some ideas at https://gcc.gnu.org/wiki/EasyHacks
You might also look at Bugzilla PRs with a lot of interest, particularly
with severity of "enhancement". In the search results screen you can
display the number of CCs and duplicates using the "change column
On Thu, Dec 15, 2022 at 07:37:35 +, Iain Sandoe wrote:
> * I have patches for clang that implements the P1184 interface which
> would allow a ‘module mapper’ to be used to discover module name <->
> pathname pairings.
>
> * The demand for the command line options we are discussing here is
18 matches
Mail list logo