public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, igusarov@akella.com, ljrittle@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: other/4957: #pragma pack(1) ... #pragma pack(4) does not restore the original alignment Date: Wed, 26 Mar 2003 09:55:00 -0000 [thread overview] Message-ID: <20030326095505.21370.qmail@sources.redhat.com> (raw) Synopsis: #pragma pack(1) ... #pragma pack(4) does not restore the original alignment Responsible-Changed-From-To: unassigned->ljrittle Responsible-Changed-By: ljrittle Responsible-Changed-When: Wed Mar 26 09:55:05 2003 Responsible-Changed-Why: Mine (only because posted from FreeBSD user). State-Changed-From-To: open->closed State-Changed-By: ljrittle State-Changed-When: Wed Mar 26 09:55:05 2003 State-Changed-Why: I am closing this report for the following reasons (please open a new report, if you like after considering this feedback and overcoming the issues I found). (a) I can confirm that g++ 3.2.2 compiles your posted *.i the same way. (b) g++ mainline can't even compile your posted *.i without error due to radical improvements in the template parser. (c) you did a great job describing the large test case (and I'm sorry if no one ever responded to you when you first posted it), however it is still not clear to me that various one-definition rule (ODR) issues are properly considered. Even though you aren't linking the code together, ODR applies for things like this. Someone that is motivated would have to sort out the test case. I attempted to build a small self-contained test case based on your findings. However: all my examples worked both with g++ 3.2 and mainline. This is why I believe your case might violate ODR. OTOH, it is also possible that your issue was related to template instantiation context botches. Since that part of the compiler is now completely revamped, your code would have to be tested against it and as I noted, your preprocessed code attachment no longer compiles. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4957
next reply other threads:[~2003-03-26 9:55 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-26 9:55 ljrittle [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-03 19:56 Loren James Rittle 2001-11-21 5:16 igusarov
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=20030326095505.21370.qmail@sources.redhat.com \ --to=ljrittle@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=igusarov@akella.com \ --cc=nobody@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).