public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63595] [5.0 Regression] Segmentation faults inside kernel
Date: Tue, 04 Nov 2014 10:18:00 -0000	[thread overview]
Message-ID: <bug-63595-4-3yCVhmOuL2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63595-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63595

--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
Merged function by IPA ICF after expand_thunk is called:

Triangulation<dim>::raw_quad_iterator Triangulation<dim>::end_quad() const
[with int dim = 3; Triangulation<dim>::raw_quad_iterator = TriaRawIterator<3,
TriaObjectAccessor<2, 3> >] (const struct Triangulation * const this)
{
  <bb 2>:
  # DEBUG this => _2(D)
  # DEBUG parent => this_3(D)
  # DEBUG level => -1
  # DEBUG index => -1
  # DEBUG local_data => 0B
  # DEBUG this => _2(D)
  # DEBUG D#265 => &MEM[(struct TriaRawIterator *)_2(D)].accessor
  # DEBUG this => D#265
  # DEBUG parent => this_3(D)
  # DEBUG level => -1
  # DEBUG index => -1
  # DEBUG local_data => 0B
  # DEBUG D#264 => &D#265->D.46601
  # DEBUG this => D#264
  # DEBUG parent => this_3(D)
  # DEBUG level => -1
  # DEBUG index => -1
  # DEBUG D.101330 => 0B
  MEM[(struct TriaAccessor *)_2(D)].present_level = -1;
  MEM[(struct TriaAccessor *)_2(D)].present_index = -1;
  MEM[(struct TriaAccessor *)_2(D)].tria = this_3(D);
  return _2(D);

}


Triangulation<dim>::raw_cell_iterator Triangulation<dim>::end() const [with int
dim = 3; Triangulation<dim>::raw_cell_iterator = TriaRawIterator<3,
CellAccessor<3> >] (const struct Triangulation * const this)
{
  <bb 2>:
  Triangulation<3>::end_quad (this_2(D)); [tail call]
  return;

}
>From gcc-bugs-return-465698-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Nov 04 10:32:52 2014
Return-Path: <gcc-bugs-return-465698-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10690 invoked by alias); 4 Nov 2014 10:32:52 -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 10671 invoked by uid 48); 4 Nov 2014 10:32:47 -0000
From: "richard at netbsd dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/63650]=?UTF-8?Q? conflicting type attributes specified for ‘virtual?=..'
Date: Tue, 04 Nov 2014 10:32: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.8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: richard at netbsd 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-63650-4-rKe6bXmeAe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63650-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63650-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-11/txt/msg00170.txt.bz2
Content-length: 499

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc650

--- Comment #8 from Richard PALO <richard at netbsd dot org> ---
(In reply to Richard PALO from comment #7)
> Further testing indicates that 'cdecl' is okay and that keeping 'regparm(0)'
> causes the error.

Is there perhaps a hint where I could checkout in the code, or is this a case
of a faulty program (in this case xulrunner)...

since this test code compiles without errors/warnings with clang++ 3.5, it
would seem that it should be okay.


  parent reply	other threads:[~2014-11-04 10:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-19 18:29 [Bug c/63595] New: " sasha.levin at oracle dot com
2014-10-19 18:34 ` [Bug tree-optimization/63595] " pinskia at gcc dot gnu.org
2014-10-19 18:48 ` sasha.levin at oracle dot com
2014-10-19 18:53 ` pinskia at gcc dot gnu.org
2014-10-20 12:53 ` rguenth at gcc dot gnu.org
2014-10-22  1:51 ` pthaugen at gcc dot gnu.org
2014-10-23 17:46 ` [Bug tree-optimization/63595] [5.0 Regression] " pthaugen at gcc dot gnu.org
2014-10-24  2:33 ` mliska at suse dot cz
2014-11-03 19:05 ` marxin at gcc dot gnu.org
2014-11-04 10:18 ` marxin at gcc dot gnu.org [this message]
2014-11-05 16:50 ` marxin at gcc dot gnu.org
2014-11-07 12:33 ` marxin 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-63595-4-3yCVhmOuL2@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).