From: Jeffrey A Law <law@cygnus.com>
To: tex_tarro@hotmail.com
Cc: help-gcc@gnu.org
Subject: Re: Compilation flags with GCC 2.8.1
Date: Tue, 05 Oct 1999 15:32:00 -0000 [thread overview]
Message-ID: <433.939135140@upchuck.cygnus.com> (raw)
In-Reply-To: <7tcgj1$jjl$1@nnrp1.deja.com>
In message < 7tcgj1$jjl$1@nnrp1.deja.com >you write:
> HP compiler has +u1 flag we didn't find in GCC compiler.
> This option is vital for our code. In fact, skipping it cause the core
> dump of our application.
Your application is in error as it performs an unaligned access.
There is no GCC option which is equivalent to +u1 from the HP compilers.
You might consider using the aligned attribute to declare mis-aligned
data structures.
jeff
WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@cygnus.com>
To: tex_tarro@hotmail.com
Cc: help-gcc@gnu.org
Subject: Re: Compilation flags with GCC 2.8.1
Date: Sun, 31 Oct 1999 13:57:00 -0000 [thread overview]
Message-ID: <433.939135140@upchuck.cygnus.com> (raw)
Message-ID: <19991031135700.SCzcLhj6lyfyKCBO38BbGJdzvX5TKws4XfcnxsV-c9o@z> (raw)
In-Reply-To: <7tcgj1$jjl$1@nnrp1.deja.com>
In message < 7tcgj1$jjl$1@nnrp1.deja.com >you write:
> HP compiler has +u1 flag we didn't find in GCC compiler.
> This option is vital for our code. In fact, skipping it cause the core
> dump of our application.
Your application is in error as it performs an unaligned access.
There is no GCC option which is equivalent to +u1 from the HP compilers.
You might consider using the aligned attribute to declare mis-aligned
data structures.
jeff
next prev parent reply other threads:[~1999-10-05 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-05 2:44 tex_tarro
1999-10-05 15:32 ` Jeffrey A Law [this message]
1999-10-31 13:57 ` Jeffrey A Law
1999-10-31 13:57 ` tex_tarro
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=433.939135140@upchuck.cygnus.com \
--to=law@cygnus.com \
--cc=help-gcc@gnu.org \
--cc=tex_tarro@hotmail.com \
/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).