From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] problem with ia64_fetch_and_add
Date: Wed, 19 Feb 2003 20:02:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805878@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805876@msgid-missing>
>>>>> On Wed, 19 Feb 2003 10:44:59 -0800, "Chen, Kenneth W" <kenneth.w.chen@intel.com> said:
Ken> I'm having problem compiling code with macro function
Ken> ia64_fetch_and_add. What happens is if I use
Ken> atomic_add_return() in one of the inline function, I'm getting
Ken> unresolved symbol error at link time for
Ken> __bad_increment_for_ia64_fetch_and_add(). But the input
Ken> argument to ia64_fetch_and_add() is of constant 1 or -1. I'm
Ken> using gcc-3.2.2.
Ken> Is this a toolchain problem? Just for the sake of compile, the
Ken> same code compiled without error with gcc-2.96, which kind of
Ken> give me a fuzzy feeling that gcc-3.2 is not working for this
Ken> case. Has anyone seen this before?
That's normally an indication that you built with too low an
optimization level (you need to use at least -O1).
--david
prev parent reply other threads:[~2003-02-19 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 18:44 [Linux-ia64] problem with ia64_fetch_and_add Chen, Kenneth W
2003-02-19 20:02 ` David Mosberger [this message]
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=marc-linux-ia64-105590709805878@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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