public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/33692] New: [4.3 Regression] Type checking error with address-of and volatile Date: Mon, 08 Oct 2007 12:08:00 -0000 [thread overview] Message-ID: <bug-33692-10053@http.gcc.gnu.org/bugzilla/> (raw) struct sndrv_pcm_info { }; typedef struct sndrv_pcm_info snd_pcm_info_t; typedef struct { snd_pcm_info_t info; } snd_pcm_shm_ctrl_t; int pcm_shm_cmd(volatile snd_pcm_shm_ctrl_t *ctrl) { snd_pcm_info((snd_pcm_info_t *) &ctrl->info); } aserver.3.min.i: In function 'pcm_shm_cmd': aserver.3.min.i:7: error: type mismatch in address expression volatile struct snd_pcm_info_t * struct snd_pcm_info_t * D.1548 = &ctrl->info aserver.3.min.i:7: internal compiler error: verify_gimple failed Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. -- Summary: [4.3 Regression] Type checking error with address-of and volatile Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: ice-on-valid-code, ice-checking Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rguenth at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33692
next reply other threads:[~2007-10-08 12:08 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-08 12:08 rguenth at gcc dot gnu dot org [this message] 2007-10-08 12:12 ` [Bug middle-end/33692] " rguenth at gcc dot gnu dot org 2007-10-09 10:57 ` rguenth at gcc dot gnu dot org 2007-10-09 11:39 ` rguenth at gcc dot gnu dot org 2007-10-09 15:52 ` rguenth at gcc dot gnu dot org 2007-10-10 9:57 ` rguenth 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-33692-10053@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).