public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos.seo at linaro dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115385] Peeling for gaps can be optimized more or needs to peel more than one iteration Date: Fri, 14 Jun 2024 16:09:57 +0000 [thread overview] Message-ID: <bug-115385-4-orT3325OBW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115385-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115385 Carlos Eduardo Seo <carlos.seo at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos.seo at linaro dot org --- Comment #4 from Carlos Eduardo Seo <carlos.seo at linaro dot org> --- This patch seems to be breaking aarch64: # 00:20:58 /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/gcc/hwint.h:266:17: error: ‘remain.poly_int<2, long unsigned int>::coeffs[0]’ may be used uninitialized [-Werror=maybe-uninitialized] # 00:20:58 /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/gcc/poly-int.h:557:7: error: ‘remain.poly_int<2, long unsigned int>::coeffs[1]’ may be used uninitialized [-Werror=maybe-uninitialized] # 00:21:48 make[3]: *** [Makefile:1199: tree-vect-stmts.o] Error 1 # 00:21:48 make[2]: *** [Makefile:5100: all-stage2-gcc] Error 2 # 00:21:48 make[1]: *** [Makefile:25572: stage2-bubble] Error 2 # 00:21:48 make: *** [Makefile:1103: all] Error 2
next prev parent reply other threads:[~2024-06-14 16:09 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-07 11:44 [Bug tree-optimization/115385] New: " rguenth at gcc dot gnu.org 2024-06-07 11:59 ` [Bug tree-optimization/115385] " rguenth at gcc dot gnu.org 2024-06-13 6:22 ` cvs-commit at gcc dot gnu.org 2024-06-13 7:15 ` rguenth at gcc dot gnu.org 2024-06-14 16:09 ` carlos.seo at linaro dot org [this message] 2024-06-14 17:31 ` sjames 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-115385-4-orT3325OBW@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).