public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/40855] undefined reference to `typeinfo for __int128'
Date: Tue, 25 Aug 2009 14:49:00 -0000	[thread overview]
Message-ID: <20090825144851.2077.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40855-14239@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from joseph at codesourcery dot com  2009-08-25 14:48 -------
Subject: Re:  undefined reference to `typeinfo for __int128'

On Tue, 25 Aug 2009, bangerth at gmail dot com wrote:

> With current mainline, I just get these errors:
> 
> g/x> /home/bangerth/bin/x86/gcc-mainline/bin/c++ x.cc -std=c++0x
> x.cc:4:36: error: '__int128_t' was not declared in this scope
> x.cc:5:36: error: '__uint128_t' was not declared in this scope
> 
> What do I need to do to make these types available?

They are only available for 64-bit targets (more precisely, 64-bit targets 
other than PA; testcases use #if (defined(__LP64__) && !defined(__hppa__)) 
|| defined(_WIN64)).


-- 


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


  parent reply	other threads:[~2009-08-25 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25  5:12 [Bug c++/40855] New: " john dot salmon at deshaw dot com
2009-08-25 14:13 ` [Bug c++/40855] " bangerth at gmail dot com
2009-08-25 14:49 ` joseph at codesourcery dot com [this message]
2009-08-25 15:26 ` bangerth at gmail dot com
     [not found] <bug-40855-4@http.gcc.gnu.org/bugzilla/>
2011-04-14 15:29 ` planet36 at gmail dot com
2011-09-25 15:07 ` paolo.carlini at oracle dot com

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=20090825144851.2077.qmail@sourceware.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).