4.3 target deprecation patch part 1: c4x removal, whole-target deprecations

Hello All, Please donot deprecate crx-*-* target. We have a active team for maintaining both crx and cr16 targets. CR16 target has been submitted for the inclusion into the 4.3. I had volunteered for maintaining the crx port earlier since the original maintainer was not with the company anymor

Re: 4.3 target deprecation patch part 1: c4x removal, whole-target deprecations

Hello Joseph S. Myers, Thanks for reply. My individual assignment process with the FSF is complete. I have submitted patches for another target CR16 and it has been reviewed. However, it has not be committed to trunk yet. OK. We will make necessary changes in the patches to include the removal

Re: 4.3 target deprecation patch part 1: c4x removal, whole-target deprecations

Yes. I donot have commit access. I will make a fresh request to commit the changes on my behalf. Thanks, Pompa Joseph S. Myers wrote: On Fri, 29 Feb 2008, Pompapathi V Gadad wrote: Hello Joseph S. Myers, Thanks for reply. My individual assignment process with the FSF is complete. I have

Re: CRX and CR16 port maintainer

I am extremely thankful to GCC Steering Committee for appointing me as maintainer for CR16 and CRX ports. I will submit the patch adding myself to the MAINTAINERS file for trunk. Can I also submit the patch for 4.3 branch? Please suggest. Thanks, Pompa David Edelsohn wrote: I am ple

Un-deprecating CRX: Request to review and commit

Hello All, Refer: http://gcc.gnu.org/ml/gcc-patches/2008-03/msg00306.html I had submitted a patch to undeprecate CRX port in 4.3 branch. The port itself has not changed. I have also submitted the tests results. So far I have not recevied any comments for GCC community. Can someone please revie

Re: Un-deprecating CRX: Request to review and commit

Hello All, Steering Committee, Can someone please review the patch and suggest if this OK for 4.3 branch? Regards, Pompa Pompapathi V Gadad wrote: Hello All, Refer: http://gcc.gnu.org/ml/gcc-patches/2008-03/msg00306.html I had submitted a patch to undeprecate CRX port in 4.3 branch. The port

Re: Un-deprecating CRX: Request to review and commit

Richard Guenther wrote: This is ok for the 4.3 branch and mainline. Thanks a lot for taking time to review the patch. May I request you to please commit the patch as I do not have write access yet. In the MAINTAINERS file Paul Woegerer is listed as maintainer for crx, is this still accurate? P

Re: Un-deprecating CRX: Request to review and commit

-04/msg01588.html http://gcc.gnu.org/ml/gcc-testresults/2008-03/msg00360.html Regards, Pompa Pompapathi V Gadad wrote: Hello All, Steering Committee, Can someone please review the patch and suggest if this OK for 4.3 branch? Regards, Pompa Pompapathi V Gadad wrote: Hello All, Refer: http

Re: Un-deprecating CRX: Request to review and commit

Richard Guenther wrote: I would suggest that you obtain svn write access as ... ... you need it anyway for updating the MAINTAINERS file. OK. I will request for the write access. However, I am afraid that 4.3.1 will be released without the patch. Pompa

Re: Un-deprecating CRX: Request to review and commit

Hello All, I have committed the patch to 4.3 branch and mainline. Thanks a lot for considering the removal of deprecation. Many thanks to all who reviewed the patch. Regards, Pompa Richard Guenther wrote: On Mon, Apr 21, 2008 at 10:40 AM, Pompapathi V Gadad <[EMAIL PROTECTED]>

Re: GCC targets need updating for new register allocator

I will look into CRX port -Pompa Joseph S. Myers wrote: The new Integrated Register Allocator is now in GCC trunk, and the old allocator is scheduled for removal on or shortly after 25 September. All GCC targets need updating for the new allocator; targets that have not been updated when the

Procedure to submit new port (CR16 processor)

aintain the CRX port? Thanks in advance, Pompa --------- Pompapathi V Gadad CR Tool Chain Team National Semiconductor Corporation

Re: Procedure to submit new port (CR16 processor)

s a lot, -Pompa --------- Pompapathi V Gadad CR Tool Chain Team National Semiconductor Corporation

libgcc fails to compile if DItype is not supported [bswapdi2]

: DWtype __bswapdi2 (DWtype u) Is the above declaration more safer for all targets? Please advice, Thanks, Pompa Pompapathi V Gadad CR Tool Chain Team National Semiconductor Corporation

Re: libgcc fails to compile if DItype is not supported [bswapdi2]

PM, Pompapathi V Gadad wrote: Hello, Current function declaration of __bswapdi2 in libgcc2.h is: DItype __bswapdi2 (DItype u) Since this declaration does not check if DItype is supported, it is bound for compilation failure for targets that do not support DItype. Would it be ok to change the DIt

Re: libgcc fails to compile if DItype is not supported [bswapdi2]

lly declare such functions in libgcc2.h. Thanks a lot for looking into this matter. I will be waiting for you next mail. Regards, Pompa Eric Christopher wrote: On Jun 20, 2007, at 9:40 PM, Pompapathi V Gadad wrote: Hello Eric, The target I am working on is 16-bit target and cannot support