From: Ulrich Drepper <drepper@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: libc-hacker@sources.redhat.com
Subject: Re: Fix unaligned access
Date: Thu, 14 Jul 2005 14:54:00 -0000 [thread overview]
Message-ID: <42D67C94.5020805@redhat.com> (raw)
In-Reply-To: <jemzop3gx1.fsf@sykes.suse.de>
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
Andreas Schwab wrote:
> Any architecture that can report unaligned accesses, which includes the
> ia64.
Not in all cases.
>>what kind of build?
>
> Care to expand?
I haven't seen any such message so it cannot happen in all builds. So
you probably did something special.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2005-07-14 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 11:21 Andreas Schwab
2005-07-13 14:25 ` Ulrich Drepper
2005-07-13 15:01 ` Andreas Schwab
2005-07-13 22:55 ` Ulrich Drepper
2005-07-14 7:56 ` Andreas Schwab
2005-07-14 7:59 ` Ulrich Drepper
2005-07-14 8:55 ` Andreas Schwab
2005-07-14 14:54 ` Ulrich Drepper [this message]
2005-07-14 15:34 ` Andreas Schwab
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=42D67C94.5020805@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=schwab@suse.de \
/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).