https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98438
--- Comment #5 from Gabriel Ravier <gabravier at gmail dot com> --- If you're wondering, the `using x = y;` syntax is roughly equivalent to `typedef y x;`, and the code just expects _Up to be the unsigned counterpart of _Tp, but here are the details as demanded by https://gcc.gnu.org/bugs/#need (sorry if the preprocessed file is a bit large, I usually use a template for examining GCC bugs): Exact version of GCC: gcc version 11.0.0 20201230 (experimental) (Compiler-Explorer-Build) System type: Assuming that's the target, x86_64-linux-gnu Options given when GCC was configured/built: ../gcc-trunk-20201231/configure --prefix=/opt/compiler-explorer/gcc-build/staging --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --disable-bootstrap --enable-multiarch --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --enable-clocale=gnu --enable-languages=c,c++,fortran,ada,d --enable-ld=yes --enable-gold=yes --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-linker-build-id --enable-lto --enable-plugins --enable-threads=posix --with-pkgversion=Compiler-Explorer-Build Complete command line that triggers the bug: g++ -g -o /tmp/compiler-explorer-compiler202101-4546-1y1nk07.gl18/output.s -masm=intel -S -fdiagnostics-color=always -O3 -std=gnu++2a -DNDEBUG -g0 /tmp/compiler-explorer-compiler202101-4546-1y1nk07.gl18/example.cpp Compiler output (error messages, warnings, etc.): (nothing) Preprocessed file (*.i*) that triggers the bug: Would have been sent as an attachment to this message but was accidentally previously sent as an attachment to a blank message, so you can find it there.
