public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spop at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/34074] Segmentation fault with -ftree-loop-linear
Date: Mon, 12 Nov 2007 17:56:00 -0000 [thread overview]
Message-ID: <20071112175603.7545.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34074-15343@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from spop at gcc dot gnu dot org 2007-11-12 17:56 -------
Subject: Re: New: Segmentation fault with -ftree-loop-linear
> Every time I try to build any project with -ftree-loop-linear gcc fault with
> segmentaion fault while processing some function from some file. Place which
> crash happens differs from project to project but presents in every project.
>
Please send a preprocessed testcase.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34074
next prev parent reply other threads:[~2007-11-12 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 15:25 [Bug tree-optimization/34074] New: " b0ntrict0r at yandex dot ru
2007-11-12 17:56 ` spop at gcc dot gnu dot org [this message]
2007-11-12 18:30 ` [Bug tree-optimization/34074] " b0ntrict0r at yandex dot ru
2007-11-12 18:32 ` b0ntrict0r at yandex dot ru
2007-12-08 20:38 ` [Bug tree-optimization/34074] Segmentation fault with -O -ftree-loop-linear pinskia at gcc dot gnu dot 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=20071112175603.7545.qmail@sourceware.org \
--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).