date:20231211

Re: Deprecating nds32--linux- target for GCC 14 (and removing it for GCC 15)

2023-12-11 Thread Jeff Law via Gcc

On 12/11/23 16:19, Andrew Pinski via Gcc wrote: nds32 support in Linux was removed last year: https://www.phoronix.com/news/Andes-Tech-NDS32-Removal The support for glibc never made it upstream as far as I can tell either. What are others thoughts on this? I believe the architecture is dead,

Re: Deprecating nds32--linux- target for GCC 14 (and removing it for GCC 15)

2023-12-11 Thread Joel Sherrill

On Mon, Dec 11, 2023 at 5:20 PM Andrew Pinski via Gcc wrote: > nds32 support in Linux was removed last year: > https://www.phoronix.com/news/Andes-Tech-NDS32-Removal > > The support for glibc never made it upstream as far as I can tell either. > > What are others thoughts on this? > Looks like a

Deprecating nds32--linux- target for GCC 14 (and removing it for GCC 15)

2023-12-11 Thread Andrew Pinski via Gcc

nds32 support in Linux was removed last year: https://www.phoronix.com/news/Andes-Tech-NDS32-Removal The support for glibc never made it upstream as far as I can tell either. What are others thoughts on this? Thanks, Andrew Pinski

Re: issue: unexpected results in optimizations

2023-12-11 Thread Dave Blanchard

Hi Jingwen, This is the same GCC which in recent versions produces something like two dozen extraneous, useless, no-op instructions when doing a simple 64-bit math operation on 32-bit systems, and does not use SSE properly either. In each major release these problems get worse. The code generat

issue: unexpected results in optimizations

2023-12-11 Thread Jingwen Wu via Gcc

Hello, I'm sorry to bother you. And I have some gcc compiler optimization questions to ask you. First of all, I used csmith tools to generate c files randomly. Meanwhile, the final running result was the checksum for global variables in a c file. For the two c files in the attachment, I performed t

issue: unexpected results in optimizations

2023-12-11 Thread Jingwen Wu via Gcc

Hello, I'm sorry to bother you. And I have some gcc compiler optimization questions to ask you. First of all, I used csmith tools to generate c files randomly. Meanwhile, the final running result was the checksum for global variables in a c file. For the two c files in the attachment, I performed t

issue: unexpected results in optimizations

2023-12-11 Thread Jingwen Wu via Gcc

Hello, I'm sorry to bother you. And I have some gcc compiler optimization questions to ask you. First of all, I used csmith tools to generate c files randomly. Meanwhile, the final running result was the checksum for global variables in a c file. For the two c files in the attachment, I performed t

issue: unexpected results in optimizations

2023-12-11 Thread Jingwen Wu via Gcc

Hello, I'm sorry to bother you. And I have some gcc compiler optimization questions to ask you. First of all, I used csmith tools to generate c files randomly. Meanwhile, the final running result is the checksum for global variables in a c file. For the two c files in the attachment, I performed th

Re: libgcov, fork, and mingw (and other targets without the full POSIX set)

2023-12-11 Thread Julian Waters via Gcc

What about removing the _gcov_fork object file from the list of object files in Makefile.in (Named LIBGCOV_INTERFACE last I remember) if the target doesn't support fork? Seems cleaner in my opinion. best regards, Julian