public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Dylan Cuthbert" <dylan@q-games.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/6144: segment-faults when using sse extensions and ia32 g++
Date: Wed, 03 Apr 2002 17:16:00 -0000	[thread overview]
Message-ID: <20020404011601.16445.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/6144; it has been noted by GNATS.

From: "Dylan Cuthbert" <dylan@q-games.com>
To: <tprince@computer.org>
Cc: <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/6144: segment-faults when using sse extensions and ia32 g++
Date: Thu, 4 Apr 2002 10:12:33 +0900

 > I find that I must use -mpreferred-stack-boundary=4 along with
 > -march=pentium3 -mfpmath=sse in order to avoid the alignment fault when
 > running on linux.  I expect this when using my preferred option -Os, but
 the
 > same occurs with other options.  I am having some difficulty on cygwin
 with
 > failure to link the namespace std methods.  I am not so proficient in c++,
 so
 > please excuse my blunders.
 > --
 > Tim Prince
 
 So you are getting the same problem on the linux platform too?  I can see
 why -mpreferred-stack-boundary=4  would work but you get the problem even
 with this option enabled (and others)?
 
 When you compile the C++ code use -L /usr/local/lib to tell g++ v3.1 to get
 its system libraries from there (for some reason it doesn't default to that
 which is odd).
 
 Regards
 
 Dylan Cuthbert
 


             reply	other threads:[~2002-04-04  1:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 17:16 Dylan Cuthbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 23:13 bangerth
2002-12-12  7:38 bangerth
2002-04-03 10:06 Tim Prince
2002-04-02 23:36 Dylan Cuthbert
2002-04-02 17:46 dylan

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=20020404011601.16445.qmail@sources.redhat.com \
    --to=dylan@q-games.com \
    --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: 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).