RE: [PATCH,RX] Support Bit Manipulation on Memory Operands

Hi, Thank you for reviewing the patch and valuable comments. You need to use match_dup instead of a matching constraint. Done. Every one that isn't explicitly invoked should have a leading * in the name. Done. Please find attached the modified patch and let me know if it's okay? Thanks

RE: [PATCH,RX] Support Bit Manipulation on Memory Operands

Hi, Thank you for reviewing the patch and valuable comments. The output constraint is now an in-out: s/=Q/+Q/. Done. Please find attached the modified patch and let me know if it's okay? Thanks Regards, Naveen rx_bit_insn.patch Description: rx_bit_insn.patch

[PATCH,RX] Support Bit Manipulation on Memory Operands

Hi, Please find attached the patch rx_bit_insn.patch which supports bit operations on memory operand. Please review the same and let me know if there should be any modifications in it. Tested with rx-elf. No new Regressions. ChangeLog 2012-11-06 Naveen H.S navee...@kpitcummins.com

RE: [H8300] Use braced strings in MD

Hi, Great. I approved it this morning and it looks like your account was created soon thereafter. Thanks for the approval. My account has been created. add yourself to the MAINTAINTERS file with write-after-approval privileges. Done. http://gcc.gnu.org/ml/gcc-cvs/2012-04/msg00705.html

PING [PATCH] RX: Fix min instruction for unsigned variables

Hi, Please consider this mail as a reminder to review the patch posted at the following link:- http://gcc.gnu.org/ml/gcc-patches/2012-04/msg00255.html Please review the patch and let us know if there should be any modifications in it. Thanks Regards, Naveen

[V850] Use braced strings in MD

Hi, Please find attached the patch v850_indent.patch that adapts V850 machine descriptions to the braced string notation. The changes makes the Machine Descriptor file more easier to read. It is similar to the following changes in SH target.

[PATCH] RX: Fix min instruction for unsigned variables

Hi, Please find attached the patch smin.patch which fixes the issue for unsigned values with min instruction. Currently, unsigned values greater than QI mode are converted into signed values and hence generates wrong value. The patch fixes the issue. Tested with rx-elf. No new regressions.

RE: [PATCH] SH2A: Don't push/pop registers for functions with resbank attribute

Hi, Looks that the patch ignores the case using movml. It could be something like the attached patch Sorry for ignoring the case using movml. Thanks for the patch which takes care of movml case. though I don't do any tests. The patch was tested with movml testcase and works as expected.

[PATCH] SH2A: Don't push/pop registers for functions with resbank attribute

Hi, Please find attached the patch resbank.patch which fixes the issue with resbank attribute. Currently, registers used in the routine are also saved on using resbank attribute. These registers are saved with resbank instruction and need not be saved separately. The patch fixes the issue.

[PATCH] SH: Fix m2a-single-only compilation error

Hi, Please find attached the patch crt1.patch which fixes compilation issue with sh2a-single-only target. Currently, compilation generates the following error:- merge of architecture 'sh3e' with architecture 'sh2a' produced unknown architecture The patch fixes the issue. Tested with sh2a-elf.

RE: toplevel *again* out of sync

Hi, Nick, Naveen, the diff between the GCC and the src commits is this; which variant is correct? -noconfigdirs=$noconfigdirs target-libgloss ${libgcj} +noconfigdirs=$noconfigdirs ${libgcj} The following variant in src is the correct version:- +noconfigdirs=$noconfigdirs

RE: SH optimized software floating point routines

Hi, I've tested sh-softfp-20100718-2131 + sh-softfp-predicate-fix on -m1, -m2, -m3, -m3 -ml, -m2a on sh-elf, sh4-linux and sh64-linux The SH toolchain was built with the following patches and regression is completed. 1. sh-softfp-20100718-2131 2. sh-softfp-predicate-fix 3. Patch by Kaz

RE: SH optimized software floating point routines

Hi. Thank you for the modified patch. I have applied the patch to gcc-4.5 sources and checking the regression for SH[1234]. I will run some more tests on the modified (patched) toolchain. I will share the test results after the regression and other tests are complete. Regards, Naveen

RE: Pseudo frame pointer register in assembly code

you can define a hard register HARD_FRAME_POINTER_REGNUM. Either way, it should not be a fixed register. In the latter case, have an elimination from FRAME_POINTER_REGNUM to HARD_FRAME_POINTER_REGNUM. Hi Ian, Thanks a lot for the useful suggestion. The HARD_FRAME_POINTER_REGNUM which

SH optimized software floating point routines

Hi, Software floating point(libgcc) routines were implemented for SH in the following links:- http://gcc.gnu.org/ml/gcc-patches/2006-09/msg00063.html http://gcc.gnu.org/ml/gcc-patches/2006-09/msg00614.html http://gcc.gnu.org/ml/gcc-patches/2004-08/msg00624.html There were some discussions

Pseudo frame pointer register in assembly code

Hi, We have been implementing GCC port for a new target. The FRAME_POINTER_REGNUM is defined a pseudo register in header file. I am using the following macros in header file to eliminate the pseudo arg pointer and frame pointer. However, there are some instances of frame pointer in the assembly

Problem in printf float values in range (-1 value 1)

Hi, We are porting gcc toolchain for a new target. Most of the functionalities are working fine as expected. However, there is one issue regarding the printf function. Issue - Float variables are prefixed by some garbage value in printf function. However, the values are generated correctly