From: Chung-Ju Wu <jasonwucj@gmail.com>
To: Chen Gang <gang.chen@asianux.com>
Cc: Jeff Law <law@redhat.com>,
Michael Schewe <michael.schewe@gmx.net>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
linux@roeck-us.net, Yoshinori Sato <ysato@users.sourceforge.jp>,
binutils@sourceware.org
Subject: Re: [Suggestion] about h8/300 architecture in gcc and binutils
Date: Fri, 13 Sep 2013 05:02:00 -0000 [thread overview]
Message-ID: <CADj25HO1-RFN-=F=A5V2vwcvENgusW5YcAf5miD6PX36p=2vHA@mail.gmail.com> (raw)
In-Reply-To: <52328621.4030408@asianux.com>
2013/9/13 Chen Gang <gang.chen@asianux.com>:
> On 09/13/2013 01:09 AM, Jeff Law wrote:
>> On 09/11/2013 10:38 PM, Chen Gang wrote:
>>> Hello all:
>>>
[...]
>>> currently, I only send 3 bugs: Bug58256, Bug58400, Bug58401, the other
>>> bugs may duplicate with these bugs, so I do not send (if they are also
>>> valuable, I will send too).
>>>
[...]
>> Please include the preprocessed source. The easiest way to get that is
>> to add the "-save-temps" option to the command line. That will create a
>> .i file which is the self-contained preprocessed code. We need that to
>> be able to debug these issues.
>>
>
> I put related ".i" files to all related bugs, please check, thanks.
>
[...]
>
> Welcome any additional information or suggestions. :-)
>
It seems that all of your cases (PR58256, PR58400, PR58401) are
related to compilation error. I think the next step is to reduce the
self-contained code that reproduces the same error for easily debugging. :)
Best regards,
jasonwucj
next prev parent reply other threads:[~2013-09-13 5:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6D39441BF12EF246A7ABCE6654B023533DC32E@LEMAIL01.le.imgtec.org>
[not found] ` <522CAAE0.5010006@redhat.com>
[not found] ` <6D39441BF12EF246A7ABCE6654B023533E40C5@LEMAIL01.le.imgtec.org>
[not found] ` <522E7255.6080301@asianux.com>
2013-09-10 1:23 ` Chen Gang
2013-09-17 13:55 ` nick clifton
2013-09-18 1:02 ` Chen Gang
[not found] ` <522E81B0.6080403@redhat.com>
2013-09-10 2:49 ` Chen Gang
2013-09-10 19:42 ` Michael Schewe
2013-09-11 1:03 ` Chen Gang
2013-09-12 4:40 ` Chen Gang
2013-09-12 17:09 ` Jeff Law
2013-09-13 3:28 ` Chen Gang
2013-09-13 5:02 ` Chung-Ju Wu [this message]
2013-09-13 5:24 ` Chen Gang
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='CADj25HO1-RFN-=F=A5V2vwcvENgusW5YcAf5miD6PX36p=2vHA@mail.gmail.com' \
--to=jasonwucj@gmail.com \
--cc=binutils@sourceware.org \
--cc=gang.chen@asianux.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=linux@roeck-us.net \
--cc=michael.schewe@gmx.net \
--cc=ysato@users.sourceforge.jp \
/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).