public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: RE: c++/8543: bus error with 2 word alignments Date: Mon, 25 Nov 2002 15:36:00 -0000 [thread overview] Message-ID: <20021119152605.3558.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8543; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Massimo Ravasi <massimo.ravasi@epfl.ch> Cc: gcc-gnats@gcc.gnu.org Subject: RE: c++/8543: bus error with 2 word alignments Date: Tue, 19 Nov 2002 09:25:53 -0600 (CST) Massimo, alignment issues are generally something that differs between processors and operating systems. Some processors cannot load doubles that are not aligned, some can. The same may apply to long long data types, but the alignment requirements of types of the same length are not necessarily the same. If a processor is told to load data from an address that is not properly aligned, it will generate a bus error. This is what you are seeing. Since alignment issues are platform dependent, it is only sensible to have the flag you describe on certain platforms only. This being said, since I don't know the requirements SunOS/SPARC has on long long data types, I cannot help you more on this. Some Sparc maintainer would have to help out here. Accessing data at a lower alignment is certainly suspicious. Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-11-19 15:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-25 15:36 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-23 15:05 nathan 2002-11-25 15:46 Wolfgang Bangerth 2002-11-25 14:55 Wolfgang Bangerth 2002-11-23 0:30 bangerth 2002-11-19 13:36 massimo.ravasi
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=20021119152605.3558.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --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).