public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/14676] New: libstdc++ atomicity.h changes of 2004-02-27 00:49:50 broke cris
Date: Mon, 22 Mar 2004 01:49:00 -0000	[thread overview]
Message-ID: <20040322014908.14676.hp@gcc.gnu.org> (raw)

You'll notice link errors referring to __exchange_and_add and __atomic_add
when linking nontrivial programs.  For example, there are large regressions in
the testsuite.  More and patch at
<URL:http://gcc.gnu.org/ml/gcc-patches/2004-03/msg01799.html>.

-- 
           Summary: libstdc++ atomicity.h changes of 2004-02-27 00:49:50
                    broke cris
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Keywords: patch
          Severity: critical
          Priority: P1
         Component: target
        AssignedTo: hp at gcc dot gnu dot org
        ReportedBy: hp at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org,mmitchel at gcc dot gnu
                    dot org
GCC target triplet: cris-*


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14676


             reply	other threads:[~2004-03-22  1:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-22  1:49 hp at gcc dot gnu dot org [this message]
2004-03-22  1:50 ` [Bug target/14676] " hp at gcc dot gnu dot org
2004-03-22  1:56 ` pinskia at gcc dot gnu dot org
2004-03-22  6:53 ` mark at codesourcery dot com
2004-03-22  7:04 ` [Bug target/14676] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-03-23 14:43 ` cvs-commit at gcc dot gnu dot org
2004-03-23 17:41 ` pinskia at gcc dot gnu dot 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=20040322014908.14676.hp@gcc.gnu.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).