From: Paolo Bolzoni <paolo.bolzoni.brown@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: -m32 and int128
Date: Wed, 01 Jan 2014 15:00:00 -0000 [thread overview]
Message-ID: <CAO4LoOw0BesY3tfugPUTfWdkmfkYxGOOKLP2eFNtiJREewh8CA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1401011431280.3653@laptop-mg.saclay.inria.fr>
Dear Marc Glisse,
thanks a lot! Your comment pointed me to the right direction,
in my distro is a different package for "64bit only" and "multilib"
gcc and I had installed the former.
On Wed, Jan 1, 2014 at 2:36 PM, Marc Glisse <marc.glisse@inria.fr> wrote:
> On Wed, 1 Jan 2014, Paolo Bolzoni wrote:
>
>> [Please put me in CC since I am not part of this list]
>>
>> Dear list,
>> I was playing around with g++ when I got this weird behavior:
>>
>> % cat a.cpp
>> #include <iostream>
>> #include <limits>
>>
>> int main() {
>> }
>>
>>
>> % g++ a.cpp
>> % g++ -m32 a.cpp
>> In file included from a.cpp:2:0:
>> /usr/include/c++/4.8.2/limits:1405:35: error: template argument 1 is
>> invalid
>> struct numeric_limits<__int128>
>> ^
>> /usr/include/c++/4.8.2/limits:1479:44: error: template argument 1 is
>> invalid
>> struct numeric_limits<unsigned __int128>
>> ^
>> %
>>
>> Compiling with -m32 breaks programs which include <limits>.
>> Is that a bug? Is there a work-around? Thanks.
>
>
> Compile with the -v flag and compare the include search paths for -m64 and
> for -m32. g++ is using the wrong bits/c++config.h with -m32, probably
> because of some variable in your environment.
>
> --
> Marc Glisse
prev parent reply other threads:[~2014-01-01 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 13:07 Paolo Bolzoni
2014-01-01 13:36 ` Marc Glisse
2014-01-01 15:00 ` Paolo Bolzoni [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=CAO4LoOw0BesY3tfugPUTfWdkmfkYxGOOKLP2eFNtiJREewh8CA@mail.gmail.com \
--to=paolo.bolzoni.brown@gmail.com \
--cc=gcc-help@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).