public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Richard Biener <rguenther@suse.de>,
	gcc-patches@gcc.gnu.org,     Jeff Law <law@redhat.com>
Subject: Re: [PATCH][4/4][v2] RPO-style value-numbering for FRE/PRE
Date: Thu, 13 Sep 2018 07:17:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.21.1809130912390.11188@anthias.pfeifer.com> (raw)
In-Reply-To: <65f272d6-8aff-7aed-b8e0-ccee6a8e7b73@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 710 bytes --]

On Mon, 10 Sep 2018, Martin Liška wrote:
> Works for me! One needed to add --wrapper gdb81,--args. So now 
> I see a nice back-trace.

Great! This appears to be a tough one, though breaking FreeBSD/i386
with clang, GCC 6 and GCC 9 (two weeks old), Solaris, HP/UX, so looks
like something around glibc vs other libcs?


On FreeBSD 10.4 I tried malloc debugging setting MALLOC_CONF=zero:true
in the environment, to zero initialize all allocations, alas that also 
did not change anything.

Nor did MALLOC_CONF=tcache:false,junk:true.

So my guess is it's a memory allocation issue, but perhaps one level 
higher than the system functions?


Not sure how I can help; clearly not my area of expertise. :-(

Gerald

  reply	other threads:[~2018-09-13  7:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24 11:24 Richard Biener
2018-09-04 22:12 ` Gerald Pfeifer
2018-09-04 22:20   ` Jeff Law
2018-09-05  7:46     ` Gerald Pfeifer
2018-09-05  7:50       ` Richard Biener
2018-09-10 11:04         ` Martin Liška
2018-09-10 12:19           ` Gerald Pfeifer
2018-09-10 12:41             ` Martin Liška
2018-09-13  7:17               ` Gerald Pfeifer [this message]
2018-09-13  7:33                 ` Richard Biener
2018-09-13  8:42                   ` Richard Biener
2018-09-13  9:25                     ` Richard Biener
2018-09-14 18:23                       ` Gerald Pfeifer
2018-09-05  6:59   ` Richard Biener
2018-09-12 19:38   ` John David Anglin

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=alpine.LSU.2.21.1809130912390.11188@anthias.pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=mliska@suse.cz \
    --cc=rguenther@suse.de \
    /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).