public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Jie Zhang <jie@codesourcery.com>,
	Ben Gamari <bgamari.foss@gmail.com>,
	  gcc@gcc.gnu.org,
	  Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: gcc- 4.6.0 20100416 rtmutex.c:1138:1: internal compiler error
Date: Tue, 20 Apr 2010 00:44:00 -0000	[thread overview]
Message-ID: <4BCCCD4B.2070906@gmail.com> (raw)
In-Reply-To: <r2s4348dea51004191417yd5915c1du89b179011d65ca5f@mail.gmail.com>

On 04/19/2010 02:17 PM, Jonathan Wakely wrote:
> On 19 April 2010 08:20, Justin P. Mattock wrote:
>> On 04/18/2010 11:57 PM, Jie Zhang wrote:
>>>
>>> On 04/19/2010 02:43 PM, Justin P. Mattock wrote:
>>>>
>>>> I couldn't resist..(had to play),
>>>> anyways I looked through the reports
>>>> but didn't see anything that was
>>>> familiar. so I went and created an entry:
>>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43791
>>>>
>>> Thanks. Please add a preprocessed source file so people can reproduce
>>> your issue.
>>>
>>>
>>
>>
>> as for the preprocessed source file,
>> not that yet skilled at code.(one day)
>
> See the "how to report" link on the gcc front page:
> http://gcc.gnu.org/bugs/
> It's not hard.
>


the info from jie, worked, as well
as: make kernel/rtmutex.i
(from joe perches)

Justin P. Mattock

      reply	other threads:[~2010-04-19 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19  5:03 Justin Mattock
2010-04-19  5:35 ` Jie Zhang
2010-04-19  6:43 ` Ben Gamari
2010-04-19  6:58   ` Justin P. Mattock
2010-04-19  7:20     ` Jie Zhang
2010-04-19  8:50       ` Justin P. Mattock
2010-04-19 21:37         ` Jonathan Wakely
2010-04-20  0:44           ` Justin P. Mattock [this message]

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=4BCCCD4B.2070906@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=bgamari.foss@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jie@codesourcery.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=linux-kernel@vger.kernel.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).