public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/18282] New: PR c/17384 patch causes regression from 3.4.2
Date: Tue, 02 Nov 2004 21:46:00 -0000	[thread overview]
Message-ID: <20041102214611.18282.jakub@gcc.gnu.org> (raw)

typedef enum { B1 = 1 } B;

B __attribute__ ((mode (QI))) b;

doesn't compile since 2004-10-13 on gcc-3_4-branch, while it is accepted
by GCC 3.3.x, 3.4.2 and current CVS HEAD.
enum with mode attribute is used e.g. by DHCP, so it would be bad if
3.4.3 was released with this.

-- 
           Summary: PR c/17384 patch causes regression from 3.4.2
           Product: gcc
           Version: 3.4.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jakub at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org,mark at codesourcery dot
                    com,rth at redhat dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18282


             reply	other threads:[~2004-11-02 21:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02 21:46 jakub at gcc dot gnu dot org [this message]
2004-11-02 21:52 ` [Bug c/18282] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-11-02 23:14 ` [Bug c/18282] " rth at gcc dot gnu dot org
2004-11-02 23:18 ` mark at codesourcery dot com
2004-11-03  7:45 ` jakub at gcc dot gnu dot org
2004-11-05  4:07 ` mmitchel at gcc dot gnu dot org
2004-11-24 22:18 ` cvs-commit at gcc dot gnu dot org
2004-12-09 18:26 ` rth at gcc dot gnu dot org
2004-12-09 22:55 ` cvs-commit at gcc dot gnu dot org
2004-12-09 22:57 ` cvs-commit at gcc dot gnu dot org
2004-12-10 19:23 ` cvs-commit at gcc dot gnu dot org
2004-12-10 19:24 ` rth at gcc dot gnu dot org
2004-12-23 23:51 ` cvs-commit 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=20041102214611.18282.jakub@gcc.gnu.org \
    --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: link
Be 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).