public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61135] It seems to be not able to call virtual method of literal object in lambda expression
Date: Sat, 10 May 2014 20:32:00 -0000	[thread overview]
Message-ID: <bug-61135-4-xMsXsBre9T@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61135-4@http.gcc.gnu.org/bugzilla/>

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

Daniel Krügler <daniel.kruegler at googlemail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daniel.kruegler@googlemail.
                   |                            |com

--- Comment #3 from Daniel Krügler <daniel.kruegler at googlemail dot com> ---
1) The problem also exists in gcc 4.10 trunk

2) As written, the presented code would be ill-formed anyway. The following
transformed example presents valid code that produces the same ICE:

//-----------------------
struct Base
{
  virtual int b() const{return 1;};
};

struct Super:Base{};

int main()
{
  constexpr Super s = Super();
  [&]{s.b();}();
}
//-----------------------
>From gcc-bugs-return-451226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 10 21:17:13 2014
Return-Path: <gcc-bugs-return-451226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5479 invoked by alias); 10 May 2014 21:17:12 -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 5402 invoked by uid 48); 10 May 2014 21:17:06 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/50751] SH Target: Displacement addressing does not work for QImode and HImode
Date: Sat, 10 May 2014 21:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: olegendo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: olegendo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-50751-4-imsOcfe8cB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-50751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-50751-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/msg00918.txt.bz2
Content-length: 1767

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

--- Comment #35 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to Oleg Endo from comment #34)
>
> I've tried to reproduce this on trunk rev 205756 (4.9) and the problem seems
> to be gone.

And it popped up again:
FAIL: gcc.dg/atomic/c11-atomic-exec-4.c  -Os  (internal compiler error)

Compiling with -Os -m4 -ml -matomic-model=soft-gusa, I get:

sh_tmp.cpp: In function 'test_thread_uint8_add':
sh_tmp.cpp:71:1: error: unable to find a register to spill in class 'R0_REGS'
sh_tmp.cpp:71:1: error: this is the insn:
(insn 29 28 30 5 (parallel [
            (set (subreg:SI (reg:QI 3 r3 [181]) 0)
                (unspec_volatile:SI [
                        (mem:QI (reg/f:SI 5 r5 [184]) [0  S1 A8])
                        (reg:QI 180)
                        (subreg:QI (reg:SI 7 r7 [178]) 0)
                    ] UNSPECV_CMPXCHG_1))
            (set (mem:QI (reg/f:SI 5 r5 [184]) [0  S1 A8])
                (unspec_volatile:QI [
                        (const_int 0 [0])
                    ] UNSPECV_CMPXCHG_2))
            (set (reg:SI 147 t)
                (unspec_volatile:SI [
                        (const_int 0 [0])
                    ] UNSPECV_CMPXCHG_3))
            (clobber (scratch:SI))
            (clobber (reg:SI 0 r0))
            (clobber (reg:SI 1 r1))
        ]) sh_tmp.cpp:71 640 {atomic_compare_and_swapqi_soft_gusa}
     (expr_list:REG_DEAD (reg:QI 180)
        (expr_list:REG_DEAD (reg:SI 7 r7 [178])
            (expr_list:REG_UNUSED (reg:SI 1 r1)
                (expr_list:REG_UNUSED (reg:SI 0 r0)
                    (nil))))))
sh_tmp.cpp:71:1: internal compiler error: in spill_failure, at reload1.c:2106

Probably we really should try switching to LRA (PR 55212).


  parent reply	other threads:[~2014-05-10 20:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-10  4:52 [Bug c++/61135] New: " okamoto6496 at gmail dot com
2014-05-10  4:54 ` [Bug c++/61135] " okamoto6496 at gmail dot com
2014-05-10  5:00 ` okamoto6496 at gmail dot com
2014-05-10  8:56 ` paolo.carlini at oracle dot com
2014-05-10 20:32 ` daniel.kruegler at googlemail dot com [this message]
2015-01-02  2:41 ` dtemirbulatov at gmail dot com
2015-04-19  0:13 ` lc289dafd7ybme05se at softbank dot ne.jp
2015-04-19  8:10 ` ubizjak at gmail 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=bug-61135-4-xMsXsBre9T@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).