From: Stefan Kempf <sisnkemp@gmail.com>
To: overseers@gcc.gnu.org
Subject: Bugzilla account creation
Date: Sun, 08 Jan 2017 15:08:00 -0000 [thread overview]
Message-ID: <20170108150818.GA26173@murdock.my-fqdn.de> (raw)
Hello,
could you please open a bugzilla account at gcc.gnu.org for
sisnkemp@gmail.com? The webpage says account creation is
filtered because of spammers.
I want to report this internal compiler error/segfault for gcc versions
6.1, 6.2, 6.3:
When compiling the example below with gcc 6.x on GNU/Linux x86_64 or
OpenBSD/amd64, gcc crashes (internal compiler error: segmentation fault)
$ gcc -O2 -pipe -c input.i
input.i: In function 'void doit()':
input.i:32:6: internal compiler error: Segmentation fault
void doit() {
^~~~
libbacktrace could not find executable to open
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
input.i:
extern "C" {
float sqrtf(float);
}
class T {
public:
float floats[1];
inline float length() const {
return sqrtf(floats[0]);
}
};
void destruct(void *);
class Container {
T Ts[1];
public:
~Container() {
destruct((void *)Ts);
}
T& operator[](int n) {
return Ts[0];
}
};
void fill(Container&);
void doit() {
Container data;
float max = 10;
int i, j, k;
for (i = 0; i < 10; i++) {
for (j = 1; j < 10; j++) {
if (max < 5)
break;
fill( data);
max = data[0].length();
for (k = 1; k < j; k++) {
max = 5;
}
}
}
}
next reply other threads:[~2017-01-08 15:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 15:08 Stefan Kempf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-02 17:46 bugzilla " example
2022-07-04 3:13 Bugzilla Account Creation 64
2022-07-04 11:22 ` Mark Wielaard
2022-05-27 16:02 Bugzilla account creation Giuseppe D'Angelo
2022-05-27 16:28 ` Mark Wielaard
2022-05-27 16:55 ` Giuseppe D'Angelo
2022-04-12 6:58 Kumar N, Bhuvanendra
2022-04-12 8:05 ` Mark Wielaard
2022-02-15 10:15 James Beddek
2022-02-15 10:41 ` Mark Wielaard
2022-01-31 15:54 bugzilla " Todd C. Miller
2022-02-01 0:03 ` Frank Ch. Eigler
2022-01-22 21:21 Bugzilla Account Creation Robert Schultz
2022-01-22 21:32 ` Mark Wielaard
2022-01-18 13:35 bugzilla account creation Christoph Anton Mitterer
2022-01-18 14:03 ` Mark Wielaard
2022-01-18 14:11 ` Christoph Anton Mitterer
2021-12-06 8:20 Bugzilla " George Rawlinson
2021-12-06 8:24 ` Mark Wielaard
2017-06-21 20:28 bugzilla " Egor Pugin
2017-06-21 20:23 Bugzilla " Felipe Magno de Almeida
2017-06-14 9:28 bugzilla " Christian Günther
2017-05-03 14:10 Bugzilla " George R.
2017-04-14 8:17 Hao Zhang
2017-04-06 21:52 Marco Atzeri
2017-03-07 14:06 Aidan Chalk
2016-12-14 4:49 bugzilla " David Starr
2016-11-14 6:39 Internal Error
2015-01-06 1:09 Bugzilla " Thomas Fanning
2014-10-20 18:27 Jonathan Gillis
2014-09-24 22:28 Karlis Senko
2013-08-01 19:07 Patrick 'P. J.' McDermott
2013-08-03 15:39 ` Ian Lance Taylor
2013-08-03 17:59 ` Patrick 'P. J.' McDermott
2013-08-03 18:11 ` Ian Lance Taylor
2013-08-08 16:10 ` Patrick 'P. J.' McDermott
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=20170108150818.GA26173@murdock.my-fqdn.de \
--to=sisnkemp@gmail.com \
--cc=overseers@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).