public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bje at au1 dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/19495] basic_string::_M_rep() can produce an unnaturally aligned pointer to _Rep
Date: Wed, 19 Jan 2005 06:05:00 -0000 [thread overview]
Message-ID: <20050119060518.2649.qmail@sourceware.org> (raw)
In-Reply-To: <20050118051448.19495.bje@gcc.gnu.org>
------- Additional Comments From bje at au1 dot ibm dot com 2005-01-19 06:05 -------
Subject: Re: basic_string::_M_rep() can produce an unnaturally aligned pointer to _Rep
On Tue, Jan 18, 2005 at 09:45:48AM -0000, pcarlini at suse dot de wrote:
> In other terms, as far as this PR is concerned, basic_string seems
> ok, just you cannot create a basic_string<char> object in memory
> aligned one, as happens in ext/array_allocator/2.cc, which therefore
> should be fixed.
Does this behaviour seem a little bit unusual to you? You said: "You
cannot create a basic_string<char> object in memory aligned one".
That is rather counter-intuitive to a user of libstdc++ who has no
understanding of the implementation details of basic_string.
Ben
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19495
next prev parent reply other threads:[~2005-01-19 6:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 5:15 [Bug libstdc++/19495] New: " bje at gcc dot gnu dot org
2005-01-18 9:18 ` [Bug libstdc++/19495] " pcarlini at suse dot de
2005-01-18 9:35 ` pcarlini at suse dot de
2005-01-18 9:46 ` pcarlini at suse dot de
2005-01-18 9:54 ` pcarlini at suse dot de
2005-01-19 6:05 ` bje at au1 dot ibm dot com [this message]
2005-01-19 6:28 ` amodra at bigpond dot net dot au
2005-01-19 9:11 ` pcarlini at suse dot de
2005-01-19 10:06 ` pcarlini at suse dot de
2005-01-19 11:52 ` pcarlini at suse dot de
2005-01-19 15:57 ` gdr at integrable-solutions dot net
2005-01-19 16:02 ` gdr at integrable-solutions dot net
2005-01-20 0:35 ` pcarlini at suse dot de
2005-01-20 4:08 ` gdr at integrable-solutions dot net
2005-01-21 12:11 ` pcarlini at suse dot de
2005-01-21 15:23 ` ncm-nospam at cantrip dot org
2005-01-21 15:37 ` ncm-nospam at cantrip dot org
2005-01-21 15:41 ` pcarlini at suse dot de
2005-01-21 15:43 ` pcarlini at suse dot de
2005-01-21 15:45 ` pcarlini at suse dot de
2005-01-21 16:39 ` ncm-nospam at cantrip dot org
2005-02-09 14:41 ` pcarlini at suse dot de
2005-02-10 0:27 ` pinskia at gcc dot gnu dot org
2005-02-10 6:07 ` janis at gcc dot gnu dot org
2005-04-01 11:42 ` pcarlini at suse dot de
2005-04-01 13:24 ` ncm at cantrip dot org
2005-04-01 13:31 ` pcarlini at suse dot de
2005-05-18 22:11 ` cvs-commit at gcc dot gnu dot org
2005-05-28 22:27 ` cvs-commit at gcc dot gnu dot org
[not found] <bug-19495-602@http.gcc.gnu.org/bugzilla/>
2009-05-14 2:55 ` bje at gcc dot gnu dot org
[not found] <bug-19495-4@http.gcc.gnu.org/bugzilla/>
2015-03-23 13:25 ` redi at gcc dot gnu.org
2023-11-08 12:32 ` redi at gcc dot gnu.org
2023-11-08 12:35 ` 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=20050119060518.2649.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: 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).