public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113467] New: [14 regression] libgcrypt-1.10.3 is miscompiled Date: Thu, 18 Jan 2024 05:21:01 +0000 [thread overview] Message-ID: <bug-113467-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113467 Bug ID: 113467 Summary: [14 regression] libgcrypt-1.10.3 is miscompiled Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org Target Milestone: --- With -O3 -march=znver2 -m32, libgcrypt-1.10.3 is miscompiled on amd64: ``` t-mpi-point: context_alloc: tv[0].'NIST P-521': sample point multiply failed: k: 7FFFFFE0003F00000007F00007FFFF80000000001FFC000000FFF030001F03E8FFFFF3E8003803E8000003EA003F0467FFFFF3E8000003E800FFE3E800000000 Qx: 7CAACB2174E1A97A63BABF4E9E6E82389898A1607E4737672B1070E5F66535E406455BFD70F2EBEEEF3F2DB9303E8DB3941190575849708A456188899714C96E74 expected Qx: 00C1002DC2884EEDADB3F9B468BBEBD55980799852C506D37271FFCD006919DB3A96DF8FE91EF6ED4B9081B1809E8F2C2B28AF5FCBF524147C73CB0B913D6FAB0995 Qy: 00990438D2386F13AC4FC5BE2F8690FC5BC1B3F5A312FD113D0DF71AD01C755A89C393087575588707247E45C22931BA45B1B9B02BE8049CD2B487CF68666DDD38D2 expected Qy: 01614E8A62C8293DD2AA6EF27D30974A4FD185019FA8EF4F982DA48698CECF706581F69EE9ED67A9C231EC9D0934D0F674646153273BCBB345E923B1EC1386A1A4AD t-mpi-point: context_alloc: tv[1].'NIST P-521': sample point multiply failed: k: 03FFF7FFFFFFFFFFFFFFE007FFFFFFE3FFFFFFFFFC01FFE0001FE02000FFFF000100000100FFFFC00100000080FFFFF040F8000001000000C100000000 Qx: 00A416B8B436A53456DBB98262BF27B80E80F9F0CA440CE867A80E56B486686837ECC41F557D4098D348EADCB8C9F05AE072EE631CE6979BA63269B698500C8F8002 expected Qx: 0172CD22CBE0634B6BFEE24BB1D350F384A945ED618ECAD48AADC6C1BC0DCC107F0FFE9FE14DC929F90153F390C25BE5D3A73A56F9ACCB0C72C768753869732D0DC4 Qy: 44D7D325D0CDEB1714AB1EE6BD62A166A2953E9799B706B49917402ACE58FF06CE207022D212958F596B0D94511FD5EC61185B6FF46B9ECBBFFBC6B1806CFCA674 expected Qy: 00D249CFB570DA4CC48FB5426A928B43D7922F787373B6182408FBC71706E7527E8414C79167F3C999FF58DE352D238F1FE7168C658D338F72696F2F889A97DE23C5 FAIL: t-mpi-point ``` Bisect said the first bad commit was one of: r14-7195-g411de96dbf2bda r14-7194-g6cb155a6cf3142 r14-7196-g99c0a540d6689e I can reproduce with: ``` wget https://gnupg.org/ftp/gcrypt/libgcrypt/libgcrypt-1.10.3.tar.bz2 tar xvf libgcrypt-1.10.3.tar.bz2 && cd libgcrypt-1.10.3 ./configure --host=i686-pc-linux-gnu --disable-doc CFLAGS="-O3 -march=znver2" CC="gcc -m32" make -j$(nproc) make -j$(nproc) check ``` The 't-mpi-point' test will fail.
next reply other threads:[~2024-01-18 5:21 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 5:21 sjames at gcc dot gnu.org [this message] 2024-01-18 5:22 ` [Bug tree-optimization/113467] " sjames at gcc dot gnu.org 2024-01-18 5:23 ` sjames at gcc dot gnu.org 2024-01-18 5:23 ` sjames at gcc dot gnu.org 2024-01-18 5:24 ` sjames at gcc dot gnu.org 2024-01-18 5:46 ` sjames at gcc dot gnu.org 2024-01-18 6:53 ` sjames at gcc dot gnu.org 2024-01-18 8:22 ` rguenth at gcc dot gnu.org 2024-01-18 8:49 ` rguenth at gcc dot gnu.org 2024-01-18 8:51 ` rguenth at gcc dot gnu.org 2024-01-18 9:32 ` sjames at gcc dot gnu.org 2024-01-18 9:35 ` sjames at gcc dot gnu.org 2024-01-18 13:16 ` rguenth at gcc dot gnu.org 2024-01-18 16:47 ` sjames at gcc dot gnu.org 2024-01-19 2:31 ` sjames at gcc dot gnu.org 2024-01-19 3:00 ` sjames at gcc dot gnu.org 2024-01-19 7:06 ` rguenth at gcc dot gnu.org 2024-01-19 11:36 ` jakub at gcc dot gnu.org 2024-01-19 13:37 ` rguenth at gcc dot gnu.org 2024-01-23 16:11 ` sjames at gcc dot gnu.org 2024-01-23 17:06 ` tnfchris at gcc dot gnu.org 2024-01-23 17:42 ` rguenther at suse dot de 2024-01-23 17:47 ` tnfchris at gcc dot gnu.org 2024-01-24 7:32 ` rguenth at gcc dot gnu.org 2024-01-26 13:28 ` rguenth at gcc dot gnu.org 2024-01-26 13:33 ` sjames at gcc dot gnu.org 2024-01-26 13:44 ` sjames at gcc dot gnu.org 2024-01-26 14:04 ` tnfchris at gcc dot gnu.org 2024-01-26 19:45 ` kacper.slominski72 at gmail dot com 2024-01-29 18:09 ` tnfchris at gcc dot gnu.org 2024-01-30 8:01 ` sjames at gcc dot gnu.org 2024-02-01 21:56 ` sjames at gcc dot gnu.org 2024-02-02 23:56 ` cvs-commit at gcc dot gnu.org 2024-02-03 22:03 ` sjames at gcc dot gnu.org 2024-02-07 10:57 ` cvs-commit at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113467-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).