procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

h8300.c, [...]: Follow spelling conventions.

Browse source 
* config/h8300/h8300.c, config/h8300/h8300.h,
	config/h8300/h8300.md: Follow spelling conventions.

From-SVN: r121562
This commit is contained in:
Kazu Hirata 2007-02-04 00:51:14 +00:00 • committed by Kazu Hirata
parent 5e32a5cf7f
commit da55315a51
4 changed files with 19 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
gcc/ChangeLog
View file

@ -1,3 +1,8 @@
2007-02-04 Kazu Hirata <kazu@codesourcery.com>
* config/h8300/h8300.c, config/h8300/h8300.h,
config/h8300/h8300.md: Follow spelling conventions.
2007-02-03 Uros Bizjak <ubizjak@gmail.com>
PR middle-end/30667

18
gcc/config/h8300/h8300.c
View file

@ -1321,20 +1321,20 @@ h8300_rtx_costs (rtx x, int code, int outer_code, int *total)
If this operand isn't a register, fall back to 'R' handling.
'Z' print int & 7.
'c' print the opcode corresponding to rtl
'e' first word of 32 bit value - if reg, then least reg. if mem
'e' first word of 32-bit value - if reg, then least reg. if mem
then least. if const then most sig word
'f' second word of 32 bit value - if reg, then biggest reg. if mem
'f' second word of 32-bit value - if reg, then biggest reg. if mem
then +2. if const then least sig word
'j' print operand as condition code.
'k' print operand as reverse condition code.
'm' convert an integer operand to a size suffix (.b, .w or .l)
'o' print an integer without a leading '#'
's' print as low byte of 16 bit value
't' print as high byte of 16 bit value
'w' print as low byte of 32 bit value
'x' print as 2nd byte of 32 bit value
'y' print as 3rd byte of 32 bit value
'z' print as msb of 32 bit value
's' print as low byte of 16-bit value
't' print as high byte of 16-bit value
'w' print as low byte of 32-bit value
'x' print as 2nd byte of 32-bit value
'y' print as 3rd byte of 32-bit value
'z' print as msb of 32-bit value
*/
/* Return assembly language string which identifies a comparison type. */
@ -1760,7 +1760,7 @@ print_operand_address (FILE *file, rtx addr)
case CONST_INT:
{
/* Since the H8/300 only has 16 bit pointers, negative values are also
/* Since the H8/300 only has 16-bit pointers, negative values are also
those >= 32768. This happens for example with pointer minus a
constant. We don't want to turn (char *p - 2) into
(char *p + 65534) because loop unrolling can build upon this

6
gcc/config/h8300/h8300.h
View file

@ -195,13 +195,13 @@ extern const char * const *h8_reg_names;
#define FUNCTION_BOUNDARY 16
/* Alignment of field after `int : 0' in a structure. */
/* One can argue this should be 32 for -mint32, but since 32 bit ints only
need 16 bit alignment, this is left as is so that -mint32 doesn't change
/* One can argue this should be 32 for -mint32, but since 32-bit ints only
need 16-bit alignment, this is left as is so that -mint32 doesn't change
structure layouts. */
#define EMPTY_FIELD_BOUNDARY 16
/* No data type wants to be aligned rounder than this.
32 bit values are aligned as such on the H8/300H and H8S for speed. */
32-bit values are aligned as such on the H8/300H and H8S for speed. */
#define BIGGEST_ALIGNMENT \
(((TARGET_H8300H || TARGET_H8300S) && ! TARGET_ALIGN_300) ? 32 : 16)

4
gcc/config/h8300/h8300.md
View file

@ -2826,7 +2826,7 @@
;; ----------------------------------------------------------------------
;;
;; We make some attempt to provide real efficient shifting. One example is
;; doing an 8 bit shift of a 16 bit value by moving a byte reg into the other
;; doing an 8-bit shift of a 16-bit value by moving a byte reg into the other
;; reg and moving 0 into the former reg.
;;
;; We also try to achieve this in a uniform way. IE: We don't try to achieve
@ -2834,7 +2834,7 @@
;; give the optimizer more cracks at the code. However, we wish to do things
;; like optimizing shifting the sign bit to bit 0 by rotating the other way.
;; There is rtl to handle this (rotate + and), but the H8/300 doesn't handle
;; 16 bit rotates. Also, if we emit complicated rtl, combine may not be able
;; 16-bit rotates. Also, if we emit complicated rtl, combine may not be able
;; to detect cases it can optimize.
;;
;; For these and other fuzzy reasons, I've decided to go the less pretty but