public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dwmw2 at infradead dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/28755] New: duplicate members of arrays Date: Wed, 16 Aug 2006 17:28:00 -0000 [thread overview] Message-ID: <bug-28755-9416@http.gcc.gnu.org/bugzilla/> (raw) See attached test case. Observe the number of times certain lines of the 'vesa_modes' array are emitted. This isn't particularly optimal, especially as it happens even with -Os. $ make cc -Os -c -o fbmon.o fbmon.i -save-temps grep 39682 fbmon.s .long 39682 .long 39682 -- Summary: duplicate members of arrays Product: gcc Version: 4.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: dwmw2 at infradead dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28755
next reply other threads:[~2006-08-16 17:28 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-08-16 17:28 dwmw2 at infradead dot org [this message] 2006-08-16 17:29 ` [Bug c/28755] " dwmw2 at infradead dot org 2006-08-16 17:36 ` [Bug middle-end/28755] " pinskia at gcc dot gnu dot org 2006-08-16 17:37 ` pinskia at gcc dot gnu dot org 2006-08-16 17:40 ` [Bug middle-end/28755] [4.0/4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2006-08-17 11:18 ` jakub at gcc dot gnu dot org 2006-08-20 22:49 ` mmitchel at gcc dot gnu dot org 2006-08-21 4:29 ` patchapp at dberlin dot org 2007-02-03 18:56 ` [Bug middle-end/28755] [4.0/4.1/4.2/4.3 " gdr at gcc dot gnu dot org 2007-02-03 20:55 ` pinskia at gcc dot gnu dot org 2007-02-14 9:21 ` mmitchel at gcc dot gnu dot org 2007-09-23 9:35 ` jakub at gcc dot gnu dot org 2007-09-24 6:36 ` [Bug middle-end/28755] [4.0/4.1/4.2 " jakub at gcc dot gnu dot org 2008-01-15 19:13 ` alexandre dot nunes at gmail dot com 2008-07-04 21:28 ` [Bug middle-end/28755] [4.2 " jsm28 at gcc dot gnu dot org 2009-03-30 17:04 ` jsm28 at gcc dot gnu dot 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-28755-9416@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).