public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mathieu Malaterre <malat@debian.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Andrew Haley <aph@redhat.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Susprising behavior of gcc on x86 (-m32)
Date: Tue, 08 Sep 2015 12:00:00 -0000	[thread overview]
Message-ID: <CA+7wUswSJ1auXVvTUxipske9JTbJbye0P42eyDhLkWh=J7jxEg@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdQ2mMTuue=+4OqL_1jpG2ET0EwCGDzhBJtHZDG=iz6F2Q@mail.gmail.com>

FYI,

On Tue, Sep 8, 2015 at 12:04 PM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
[...]
> That's not the only option. You could compile one file with GCC and
> all others with Clang and see if you can reproduce it. Repeat for each
> file, which will narrow down the file where the problem occurs. Then
> you can try splitting that file into smaller pieces, with one function
> per file, and repeat the process. That would tell you which function
> or functions get miscompiled by GCC.

Ok so if I compile eveything with gcc and then only `tcd.c` using
clang, then everything works as expected (no symptoms).
ref: https://github.com/uclouvain/openjpeg/blob/master/src/lib/openjp2/tcd.c

I'll repeat your approach to find the culprit function.

  parent reply	other threads:[~2015-09-08 12:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  9:15 Mathieu Malaterre
2015-09-08  9:45 ` Andrew Haley
2015-09-08  9:57   ` Mathieu Malaterre
2015-09-08 10:05     ` Jonathan Wakely
2015-09-08 10:15       ` Mathieu Malaterre
2015-09-08 10:21       ` Mathieu Malaterre
2015-09-08 10:36         ` Jonathan Wakely
2015-09-08 11:38           ` Mathieu Malaterre
2015-09-08 12:00       ` Mathieu Malaterre [this message]
2015-09-08 12:40         ` Mathieu Malaterre
2015-09-08 13:16           ` Markus Trippelsdorf
2015-09-08 13:19             ` Mathieu Malaterre
2015-09-08 13:17           ` Mathieu Malaterre
2015-09-08 13:23           ` Andrew Haley

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='CA+7wUswSJ1auXVvTUxipske9JTbJbye0P42eyDhLkWh=J7jxEg@mail.gmail.com' \
    --to=malat@debian.org \
    --cc=aph@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    /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).