public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gdr at cs dot tamu dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/8670] Alignment problem in std::basic_string Date: Sat, 16 Oct 2004 14:48:00 -0000 [thread overview] Message-ID: <20041016144822.700.qmail@sourceware.org> (raw) In-Reply-To: <20021121063601.8670.jkanze@caicheuvreux.com> ------- Additional Comments From gdr at cs dot tamu dot edu 2004-10-16 14:48 ------- Subject: Re: Alignment problem in std::basic_string "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org> writes: | I see this report is marked as a v3 report. I do not understand exactly what | you still need to fix in C++. I have a patch in my (long) queue which fixes | this: | | template <int> | struct S { | enum { K = 8 }; | char foo __attribute__((aligned(K))); | }; | | Can I assume that this bug is about this issue, and thus assigning this to me | (if Gaby does not mind) or is it better if I open a new report? I don't mind you take on bugs, as far as they are fixed :-) The V3 bits in this is that we need to get basic_string fixed. If the front-end ix fixed, then we can use the aligned attribute in a meaningful way. Thanks -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8670
next prev parent reply other threads:[~2004-10-16 14:48 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20021121063601.8670.jkanze@caicheuvreux.com> 2003-10-01 21:47 ` pinskia at gcc dot gnu dot org 2003-10-01 22:05 ` gdr at integrable-solutions dot net 2004-10-16 11:06 ` giovannibajo at libero dot it 2004-10-16 11:10 ` giovannibajo at libero dot it 2004-10-16 12:39 ` giovannibajo at libero dot it 2004-10-16 14:48 ` gdr at cs dot tamu dot edu [this message] 2004-10-16 15:14 ` giovannibajo at libero dot it 2004-10-16 20:09 ` pcarlini at suse dot de 2005-01-18 9:19 ` pcarlini at suse dot de 2005-01-21 17:46 ` ncm-nospam at cantrip dot org 2005-01-21 17:53 ` pcarlini at suse dot de 2005-01-23 3:52 ` ncm-nospam at cantrip dot org 2005-01-23 10:30 ` pcarlini at suse dot de 2005-01-24 3:42 ` ncm-nospam at cantrip dot org 2005-01-24 9:45 ` pcarlini at suse dot de 2005-01-24 11:06 ` pcarlini at suse dot de 2005-01-31 5:29 ` ncm-nospam at cantrip dot org 2005-04-01 13:32 ` pcarlini at suse dot de [not found] <bug-8670-4113@http.gcc.gnu.org/bugzilla/> 2007-04-03 15:30 ` jamesc at dspsrv dot com 2007-04-03 18:26 ` pcarlini at suse dot de [not found] <bug-8670-4@http.gcc.gnu.org/bugzilla/> 2023-11-08 16:45 ` redi at gcc dot gnu.org 2023-11-08 16:47 ` redi at gcc dot gnu.org 2023-11-08 19:00 ` redi 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=20041016144822.700.qmail@sourceware.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: 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).