Gcc  - Animation Software

2022-11-17 Thread Kathy Wood via Gcc
Hi Gcc , I’m emailing you to see if you would be interested in the data list of “Animation Software” Users, Clients and Customers at discounted price? Henceforth, we maintain a valid and updated data list of the following technology users: * Adobe After Effects * Renderforest * Animaker *

Re: size_t vs long.

2022-11-17 Thread Alejandro Colomar via Gcc
Hi Paul, On 11/17/22 22:39, Paul Eggert wrote: Second and more important, that code is bogus. Nobody should ever write code like that. If I wrote code like that, I'd *want* a trap. for (size_t i = 41; i < sizeof A / sizeof A[0]; --i) {    A[i] = something_nice; } The code above seems a bug by

gcc-10-20221117 is now available

2022-11-17 Thread GCC Administrator via Gcc
Snapshot gcc-10-20221117 is now available on https://gcc.gnu.org/pub/gcc/snapshots/10-20221117/ 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: How can Autoconf help with the transition to stricter compilation defaults?

2022-11-17 Thread Paul Eggert
On 11/17/22 13:35, Bruno Haible wrote: Clang will surely not acquire knowledge about "every library", right, only about the C library according to relevant standards (ISO C, POSIX)? I don't know the Clang developers' plans. But if I wanted Clang to be picky then yes, I'd have it know about ev

Re: How can Autoconf help with the transition to stricter compilation defaults?

2022-11-17 Thread Bruno Haible
Paul Eggert wrote: > > AC_CHECK_FUNC *should not* just probe for linkability of a symbol > > ... Autoconf cannot > be expected to know every signature of every function in every library. Clang will surely not acquire knowledge about "every library", right, only about the C library according to

Re: How can Autoconf help with the transition to stricter compilation defaults?

2022-11-17 Thread Paul Eggert
On 2022-11-16 10:59, Zack Weinberg wrote: I'm generally in agreement with Rich Felker's argument (inhttps://ewontfix.com/13/) that AC_CHECK_FUNC*should not* just probe for linkability of a symbol So am I. I'm not saying Autoconf should never change here, only that the change would not be tr

Re: How can Autoconf help with the transition to stricter compilation defaults?

2022-11-17 Thread Paul Eggert
On 2022-11-16 10:40, Jeffrey Walton wrote: This line of arguments is not persuasive. It is full of logical fallacies. ... none of which you stated. No matter how we solve the problem, it will be a hack that exploits "logical fallacies" (whatever that means). However, a reaction "You violated

Announce: GNU MPFR 4.1.1 is released

2022-11-17 Thread Vincent Lefevre
GNU MPFR 4.1.1 ("épinards à la crème", patch level 1), a C library for multiple-precision floating-point computations with correct rounding, is now available for download from the MPFR web site: https://www.mpfr.org/mpfr-4.1.1/ and from the GNU FTP site: https://ftp.gnu.org/gnu/mpfr/ Thanks

Re: "random" segment faults in expect running GCC regression test on LoongArch

2022-11-17 Thread Xi Ruoyao via Gcc
On Wed, 2022-11-09 at 15:43 +0800, Xi Ruoyao wrote: > Hi, > > This is a "help wanted" message.  When I run GCC regression test on > loongarch64-linux-gnu, expect occasionally crashes with a segment fault. > The stack backtrace is like: /* snip */ > The crashes happen on both my own LoongArch boa

Re: How can Autoconf help with the transition to stricter compilation defaults?

2022-11-17 Thread Jason Merrill via Gcc
On Sat, Nov 12, 2022 at 7:44 PM Paul Eggert wrote: > On 2022-11-11 07:11, Aaron Ballman wrote: > > Clang doesn't require such a linker (we work with various system > linkers). > > As long as the system linkers continue to work as they have > traditionally worked, we're fine. > > > the frontend pe

Re: How can Autoconf help with the transition to stricter compilation defaults?

2022-11-17 Thread Michael Matz via Gcc
Hello, On Wed, 16 Nov 2022, Paul Eggert wrote: > On 2022-11-16 06:26, Michael Matz wrote: > > char foobar(void); > > int main(void) { > >return &foobar != 0; > > } > > That still has undefined behavior according to draft C23, This is correct (and also holds for the actually working variant