From: Michael Schewe <michael.schewe@gmx.net>
To: Chen Gang <gang.chen@asianux.com>
Cc: Jeff Law <law@redhat.com>, "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: Tue, 10 Sep 2013 19:42:00 -0000 [thread overview]
Message-ID: <522F791E.2060603@gmx.net> (raw)
In-Reply-To: <522E888A.2060005@asianux.com>
Hello Maintainers,
if you like to drop h8/300 support in linux kernel, thats OK for me.
But i like to see it still supported in gcc & binutils, at least i have some projects and know companies using this architecture in embedded applications, bare
metal without OS. These products have lifetime in range of 10...20 years and need toolchain support for software-updates.
Michael
Please note for answers: i am only subscribed to binutils mailing list.
Chen Gang schrieb:
> On 09/10/2013 10:19 AM, Jeff Law wrote:
>> On 09/09/2013 07:13 PM, Chen Gang wrote:
>>> Hello Maintainers:
>>>
>>> After google search and check the Linux kernel, H8/300 is dead, and for
>>> gcc-4.9.0 and binutils-2.23.2 still has h8300, do we still need it for
>>> another OS ?
>>>
>>> Welcome any suggestions or completions, thanks.
>>>
>>>
>>> The related information in linux kernel next tree:
>>>
>>> commit d02babe847bf96b82b12cc4e4e90028ac3fac73f
>>> Author: Guenter Roeck<linux@roeck-us.net>
>>> Date: Fri Aug 30 06:01:49 2013 -0700
>>>
>>> Drop support for Renesas H8/300 (h8300) architecture
>>>
>>> H8/300 has been dead for several years, and the kernel for it
>>> has not compiled for ages. Drop support for it.
>>>
>>> Cc: Yoshinori Sato<ysato@users.sourceforge.jp>
>>> Acked-by: Greg Kroah-Hartman<gregkh@linuxfoundation.org>
>>> Signed-off-by: Guenter Roeck<linux@roeck-us.net>
>>>
>>>
>>> The related information in gcc/binutils:
>>>
>>> We can build h8300 cross-compiler for Linux kernel, successfully,
>>> but it has many bugs when building Linux kernel with -Os.
>>> if we still need h8300 for another OS, is it still valuable to send
>>> these bugs to Bugzilla (although it is found under Linux)?
>> It is still useful to send code generation bugs for the H8/300 series to
>> the GCC folks.
>>
>
> OK, thanks, I will wait for 1-2 days which may get another members'
> opinions for discussing.
>
> If no additional opinions, I will report them to Bugzilla, and I should
> try to continue 'work' with related members (although I am a newbie for
> compiler and binutils programming).
>
>> jeff
>>
>>
>>
>
> Thanks.
next prev parent reply other threads:[~2013-09-10 19:42 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 [this message]
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
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=522F791E.2060603@gmx.net \
--to=michael.schewe@gmx.net \
--cc=binutils@sourceware.org \
--cc=gang.chen@asianux.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.com \
--cc=linux@roeck-us.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).