public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/61091] New: [4.10 Regression] wide-int.h:1172:45: error: incomplete type ‘wi::int_traits<long long unsigned int>’ used in nested name specifier
Date: Wed, 07 May 2014 03:43:00 -0000	[thread overview]
Message-ID: <bug-61091-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 61091
           Summary: [4.10 Regression] wide-int.h:1172:45: error:
                    incomplete type ‘wi::int_traits<long long unsigned
                    int>’ used in nested name specifier
           Product: gcc
           Version: 4.10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: danglin at gcc dot gnu.org
              Host: hppa-unknown-linux-gnu
            Target: hppa-unknown-linux-gnu
             Build: hppa-unknown-linux-gnu

g++-4.9 -c   -g -DIN_GCC    -fno-exceptions -fno-rtti
-fasynchronous-unwind-tabl
es -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-format
-Wmissing-for
mat-attribute -Woverloaded-virtual -pedantic -Wno-long-long
-Wno-variadic-macros
 -Wno-overlength-strings -fno-common  -DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc
-I
../../gcc/gcc/. -I../../gcc/gcc/../include -I../../gcc/gcc/../libcpp/include 
-I
../../gcc/gcc/../libdecnumber -I../../gcc/gcc/../libdecnumber/dpd
-I../libdecnum
ber -I../../gcc/gcc/../libbacktrace -DCLOOG_INT_GMP    -o loop-iv.o -MT
loop-iv.
o -MMD -MP -MF ./.deps/loop-iv.TPo ../../gcc/gcc/loop-iv.c
In file included from ../../gcc/gcc/real.h:25:0,                 from
../../gcc/gcc/rtl.h:27,
                 from ../../gcc/gcc/loop-iv.c:54:
../../gcc/gcc/wide-int.h: In instantiation of
‘fixed_wide_int_storage<N>::fixed_
wide_int_storage(const T&) [with T = long long unsigned int; int N =
160]’:../../gcc/gcc/wide-int.h:724:15:   required from
‘generic_wide_int<T>::generic_w
ide_int(const T&) [with T = long long unsigned int; storage =
fixed_wide_int_sto
rage<160>]’
../../gcc/gcc/loop-iv.c:2628:48:   required from here
../../gcc/gcc/wide-int.h:1172:45: error: incomplete type ‘wi::int_traits<long
lo
ng unsigned int>’ used in nested name specifier
   WI_BINARY_RESULT (T, FIXED_WIDE_INT (N)) *assertion ATTRIBUTE_UNUSED;
   WI_BINARY_RESULT (T, FIXED_WIDE_INT (N)) *assertion ATTRIBUTE_UNUSED;
                                             ^
../../gcc/gcc/wide-int.h:1173:47: error: incomplete type ‘wi::int_traits<long
lo
ng unsigned int>’ used in nested name specifier
   wi::copy (*this, WIDE_INT_REF_FOR (T) (x, N));
                                               ^
Makefile:1058: recipe for target 'loop-iv.o' failed
make[3]: *** [loop-iv.o] Error 1
>From gcc-bugs-return-450747-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 07 04:38:06 2014
Return-Path: <gcc-bugs-return-450747-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11229 invoked by alias); 7 May 2014 04:38:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11202 invoked by uid 48); 7 May 2014 04:38:01 -0000
From: "greened at obbligato dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61082] [x86-64 Itanium ABI] g++ uses wrong return location for class with head padding
Date: Wed, 07 May 2014 04:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: greened at obbligato dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61082-4-w070zIuTDS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61082-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61082-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-05/txt/msg00439.txt.bz2
Content-length: 388

http://gcc.gnu.org/bugzilla/show_bug.cgi?ida082

--- Comment #3 from David Greene <greened at obbligato dot org> ---
(In reply to Andrew Pinski from comment #2)
> Y is a non-POD.

So...?

The ABI doesn't talk about POD vs. non-POD.  It talks about copy constructors
and destructors.

Can you explain what POD has to do with this and why Intel generates the return
value in (RAX, RDX)?


             reply	other threads:[~2014-05-07  3:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07  3:43 danglin at gcc dot gnu.org [this message]
2014-05-07  8:27 ` [Bug other/61091] " rguenth at gcc dot gnu.org
2014-05-07 10:31 ` rsandifo at gcc dot gnu.org
2014-05-07 13:42 ` dave.anglin at bell dot net
2014-05-08  0:57 ` danglin at gcc dot gnu.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=bug-61091-4@http.gcc.gnu.org/bugzilla/ \
    --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).