compile - Search results
Mailing lists >> pgsql-hackers >> Thread
2025-06-10 17:28:11 | Re: Non-reproducible AIO failure (Konstantin Knizhnik)
compiler. Why it is better reproduced in debug build? May be because of timing. Or may be because
Mailing lists >> pgsql-hackers >> Thread
2025-06-09 02:05:29 | Re: Non-reproducible AIO failure (Thomas Munro)
compiled by MacPorts/whatever) for each major version and finding new strings, ie strings that don't appear
Mailing lists >> pgsql-hackers >> Thread
2025-06-07 16:27:45 | Re: Non-reproducible AIO failure (Konstantin Knizhnik)
compiler bug. The generated code (clang 16) overwrites all three bitfields but looks like is doing
Mailing lists >> pgsql-hackers >> Thread
2025-06-07 07:00:00 | Re: Non-reproducible AIO failure (Alexander Lakhin)
compiled by Ubuntu clang version 18.1.3 (1ubuntu1), 64-bit On that my MacBook, the triplet
Mailing lists >> pgsql-hackers >> Thread
2025-06-06 22:21:13 | Re: Non-reproducible AIO failure (Tom Lane)
compiler bug. The C standard explicitly allows compilers to use word-wide operations to access
Mailing lists >> pgsql-hackers >> Thread
2025-06-06 21:47:32 | Re: Non-reproducible AIO failure (Andres Freund)
compilers / versions were you comparing? I don't quite see similar assembly... I'm annotating
Mailing lists >> pgsql-hackers >> Thread
2025-06-06 09:13:57 | Re: Non-reproducible AIO failure (Konstantin Knizhnik)
compiler. Bitfields with different enum type looks really exotic, so no wonder that optimizer can do something
Mailing lists >> pgsql-hackers >> Thread
2025-06-06 01:13:52 | Re: Non-reproducible AIO failure (Matthias van de Meent)
decompiled code generated for pgaio_io_before_start and pgaio_io_start_readv. pgaio_io_start
Mailing lists >> pgsql-hackers >> Thread
2025-05-27 17:10:15 | Re: Non-reproducible AIO failure (Tom Lane)
compiler is really $ gcc -v Apple clang version 17.0.0 (clang-1700.0.13.3) Target: arm64-apple-darwin24.5.0