public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sumanth Gundapaneni <Sumanth.Gundapaneni@kpitcummins.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	"Jayant R. Sonar"	<Jayant.Sonar@kpitcummins.com>
Subject: RE: CR16 Port addition
Date: Wed, 29 Dec 2010 15:32:00 -0000	[thread overview]
Message-ID: <371569CBCFB2E745B891DBB88B2DFDDD19EAB646DB@KCINPUNHJCMS01.kpit.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1012221149510.4347@digraph.polyomino.org.uk>

Hi Joseph,

Thanks for your detailed review and useful suggestions.

>> Files built for the target need to have the exception wording 
>> referencing COPYING.RUNTIME, not no exception as here ...

>> ... or the old GPLv2 exception as here.  Please check all libgcc
>> sources in this patch for appropriate license exception wording.

The concerned files have been modified as per GPLv3.

>> In general, if possible files built for the target should be under 
>> libgcc/config not gcc/config with makefile rules under 
>> libgcc/config as well.

The files have been moved to libgcc/config.

>> Could you clarify how these source files are related to the main 
>> target-independent unwind-dw2* files 

The following link was referenced while implementing CPP Exception 
Handling for CR16. http://gcc.gnu.org/wiki/Dwarf2EHNewbiesHowto
As per the link, required changes were implemented to handle 
exceptions in C++.

However, the CR16's programming memory is 2-byte aligned and the least
significant bit of PC is always zero. The Return Address (RA) register 
always saves the value of PC right shifted by 1(PC >> 1). This 
conversion seems broken at some places during unwinding which results 
in terminate() function  being called.
 
These files were added to help fix this problem. However, we have not yet
completely solved this problem. If we are able to fix this without major 
modifications, we will move these files back in which case customized
unwind files would not be needed.

>> No, never send such a patch to gcc-patches.  Any such changes must 
>> go to config-patches 
>> GCC should not have any local changes, and the GCC and src 
>> repositories should be kept in sync.

Fortunately, config.git has cr16 target added long time back. 


Thanks and Regards,
Sumanth G


  reply	other threads:[~2010-12-29 13:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 11:58 Sumanth Gundapaneni
2010-12-22 13:25 ` Joseph S. Myers
2010-12-29 15:32   ` Sumanth Gundapaneni [this message]
2011-01-13  9:06 Sumanth Gundapaneni
2011-01-14 18:54 ` Richard Henderson
2011-04-08 13:26 Sumanth Gundapaneni
2011-04-08 14:56 ` Joseph S. Myers
2011-05-20 13:59   ` Sumanth Gundapaneni
2011-05-20 17:07     ` Joseph S. Myers
2011-05-30 15:44       ` Sumanth Gundapaneni
2011-06-09 10:15       ` Sumanth Gundapaneni
2011-06-28  8:32       ` Sumanth Gundapaneni
2011-07-15  7:54       ` Sumanth Gundapaneni

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=371569CBCFB2E745B891DBB88B2DFDDD19EAB646DB@KCINPUNHJCMS01.kpit.com \
    --to=sumanth.gundapaneni@kpitcummins.com \
    --cc=Jayant.Sonar@kpitcummins.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    /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).