public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mason <slash.tmp@free.fr>
To: Matt Sexton <matt.sexton@redlinetrading.com>
Cc: GCC help <gcc-help@gcc.gnu.org>
Subject: Re: internal compiler error
Date: Mon, 22 Jan 2018 13:14:00 -0000	[thread overview]
Message-ID: <64e8fad2-4708-83e4-1d78-d669c33ee3a5@free.fr> (raw)
In-Reply-To: <CAMp6Wr9L3A-Yr1rAMFYxW2-DeaDb1havbucRioLN7XNm4FWNfQ@mail.gmail.com>

On 19/01/2018 14:16, Matt Sexton wrote:

> I am encountering an internal compiler error when compiling with -O2

Is there any way to get mingw-w64 7.2 short of installing a full-blown
distro, or compiling from source?

Do the following testcases (slight variations on the one you provided)
also cause an ICE?

I used the following command-line:
gcc-7 -Wall -Wextra -std=gnu11 -O2 -S testcase.c


TESTCASE 1

struct b {
	struct { int a[0]; };
};
struct d { int c; };
__thread struct d e;
extern int f;
extern void foo(int i);
void g(void)
{
  struct b *h = &e.c;
  int *a = h->a;
  foo(a[f]);
  foo(a[f]);
}


TESTCASE 2

struct b {
	struct { int a[4]; };
};
struct d { int c; };
__thread struct d e;
extern int f;
extern void foo(int i);
void g(void)
{
  struct b *h = &e.c;
  int *a = h->a;
  foo(a[f]);
  foo(a[f]);
}


TESTCASE 3

struct b {
	struct { int a[1]; };
};
struct d { int c; };
struct d e;
extern int f;
extern void foo(int i);
void g(void)
{
  struct b *h = &e.c;
  int *a = h->a;
  foo(a[f]);
  foo(a[f]);
}


Regards.

  parent reply	other threads:[~2018-01-22 13:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 13:17 Matt Sexton via gcc-help
2018-01-19 13:26 ` Mikhail Maltsev
2018-01-19 14:35   ` Matt Sexton via gcc-help
2018-01-19 15:54     ` Matt Sexton via gcc-help
2018-01-22 13:14 ` Mason [this message]
2018-01-22 13:21   ` Matt Sexton via gcc-help
  -- strict thread matches above, loose matches on Subject: below --
2012-12-24 16:44 Internal Compiler Error tanle
2012-12-24 18:19 ` Andrew Haley
2012-12-27 17:27 ` Iyer, Balaji V
2010-07-12  9:04 internal compiler error Malte.Mauelshagen
2010-07-12  9:56 ` Ian Lance Taylor
2008-02-29 21:27 raian.ufop
2008-02-29 22:16 ` Brian Dessent
2008-03-03 18:50   ` raian.ufop
2003-07-30 20:29 Internal " DEEPA SIVASANKARANE
2001-07-03  8:36 Av Vl
2001-07-02  8:04 Av Vl
1999-09-29 12:58 Guardian
1999-09-30  3:33 ` jwk
1999-09-30 23:56   ` jwk
1999-10-01  0:00   ` jwk
1999-10-01 13:49   ` Guardian
1999-10-31 13:57     ` Guardian
1999-09-30 23:56 ` Guardian
1999-10-01  0:00 ` Guardian

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=64e8fad2-4708-83e4-1d78-d669c33ee3a5@free.fr \
    --to=slash.tmp@free.fr \
    --cc=gcc-help@gcc.gnu.org \
    --cc=matt.sexton@redlinetrading.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).