Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?

2023-06-05 Thread Gabriel Ravier via Gcc
On 6/6/23 02:09, Dave Blanchard wrote: On Tue, 6 Jun 2023 01:59:42 +0200 Gabriel Ravier wrote: [nothing of value] If this guy's threads are such a terrible waste of your time, how about employing your email client's filters to ignore his posts (and mine too) and fuck off? Now YOU'RE wastin

Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?

2023-06-05 Thread Paul Koning via Gcc
> On Jun 5, 2023, at 8:09 PM, Dave Blanchard wrote: > > On Tue, 6 Jun 2023 01:59:42 +0200 > Gabriel Ravier wrote: > >> [nothing of value] > > If this guy's threads are such a terrible waste of your time, how about > employing your email client's filters to ignore his posts (and mine too) a

Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?

2023-06-05 Thread Dave Blanchard
On Tue, 6 Jun 2023 01:59:42 +0200 Gabriel Ravier wrote: > [nothing of value] If this guy's threads are such a terrible waste of your time, how about employing your email client's filters to ignore his posts (and mine too) and fuck off? Now YOU'RE wasting everyone's time, as your type is so s

Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?

2023-06-05 Thread Gabriel Ravier via Gcc
On 6/6/23 00:23, Dave Blanchard wrote: On Mon, 5 Jun 2023 13:35:22 +0200 Gabriel Ravier via Gcc wrote: [pages of bullshit deleted] 2. Are you aware that these emails are not only pretty useless, but potentially actively counterproductive ? I'd personally expect GCC developers, who are rightfu

Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?

2023-06-05 Thread Dave Blanchard
On Mon, 5 Jun 2023 13:35:22 +0200 Gabriel Ravier via Gcc wrote: > [pages of bullshit deleted] > > 2. Are you aware that these emails are not only pretty useless, but > potentially actively counterproductive ? I'd personally expect GCC > developers, who are rightfully not particularly happy at t

GNU Tools Cauldron 2023

2023-06-05 Thread Richard Earnshaw via Gcc
We are pleased to invite you all to the next GNU Tools Cauldron, taking place in Cambridge, UK, on September 22-24, 2023. As for the previous instances, we have setup a wiki page for details: https://gcc.gnu.org/wiki/cauldron2023 Like last year, we are having to charge for attendance. W

Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?

2023-06-05 Thread Julian Waters via Gcc
gcc -O0 -c -mabm -mbmi retard.c -o retard.o ^ | | | int code(unsigned long long number) { return (int) _tzcnt_u64(number); } objdump --disassemble-all retard.o : 0: 55 push %rbp 1: 48 89 e5

Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?

2023-06-05 Thread Gabriel Ravier via Gcc
On 6/5/23 12:17, Stefan Kanthak wrote: --- failure.c --- int _clz(unsigned long long argument) { return __builtin_clzll(argument); } int _ctz(unsigned long long argument) { return __builtin_ctzll(argument); } --- EOF --- GCC 13.1-m32 -mabm -mbmi -mlzcnt -O3 failure.c

Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?

2023-06-05 Thread Jonathan Wakely via Gcc
https://gcc.gnu.org/bugs/

Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?

2023-06-05 Thread Stefan Kanthak
--- failure.c --- int _clz(unsigned long long argument) { return __builtin_clzll(argument); } int _ctz(unsigned long long argument) { return __builtin_ctzll(argument); } --- EOF --- GCC 13.1-m32 -mabm -mbmi -mlzcnt -O3 failure.c _clz(unsigned long lo