diff options
| author | Joern Rennecke <amylaar@spamcop.net> | 2011-01-19 15:23:06 +0000 |
|---|---|---|
| committer | Joern Rennecke <amylaar@gcc.gnu.org> | 2011-01-19 15:23:06 +0000 |
| commit | b899fd784b2e89080c853afd5bb1776328c9d4e7 (patch) | |
| tree | 61d760d08b33ace1f32c11078ec43d5980b02e04 /gcc | |
| parent | 2e0642cde2ace61ba98145609d5f62796666cbfa (diff) | |
| download | gcc-b899fd784b2e89080c853afd5bb1776328c9d4e7.zip gcc-b899fd784b2e89080c853afd5bb1776328c9d4e7.tar.gz gcc-b899fd784b2e89080c853afd5bb1776328c9d4e7.tar.bz2 | |
tm.texi.in: Spell out that a lack of register class unions can lead to ICEs.
* doc/tm.texi.in: Spell out that a lack of register class unions
can lead to ICEs.
* doc/tm.texi: Regenerate.
From-SVN: r168998
Diffstat (limited to 'gcc')
| -rw-r--r-- | gcc/ChangeLog | 6 | ||||
| -rw-r--r-- | gcc/doc/tm.texi | 4 | ||||
| -rw-r--r-- | gcc/doc/tm.texi.in | 4 |
3 files changed, 12 insertions, 2 deletions
diff --git a/gcc/ChangeLog b/gcc/ChangeLog index b799162..9af2456 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,9 @@ +2011-01-19 Joern Rennecke <amylaar@spamcop.net> + + * doc/tm.texi.in: Spell out that a lack of register class unions + can lead to ICEs. + * doc/tm.texi: Regenerate. + 2011-01-19 Jakub Jelinek <jakub@redhat.com> PR rtl-optimization/47337 diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi index 010e77b..e3325b0 100644 --- a/gcc/doc/tm.texi +++ b/gcc/doc/tm.texi @@ -2341,7 +2341,9 @@ You should define a class for the union of two classes whenever some instruction allows both classes. For example, if an instruction allows either a floating point (coprocessor) register or a general register for a certain operand, you should define a class @code{FLOAT_OR_GENERAL_REGS} -which includes both of them. Otherwise you will get suboptimal code. +which includes both of them. Otherwise you will get suboptimal code, +or even internal compiler errors when reload cannot find a register in the +the class computed via @code{reg_class_subunion}. You must also specify certain redundant information about the register classes: for each class, which classes contain it and which ones are diff --git a/gcc/doc/tm.texi.in b/gcc/doc/tm.texi.in index 3298c3d..1a5f040 100644 --- a/gcc/doc/tm.texi.in +++ b/gcc/doc/tm.texi.in @@ -2331,7 +2331,9 @@ You should define a class for the union of two classes whenever some instruction allows both classes. For example, if an instruction allows either a floating point (coprocessor) register or a general register for a certain operand, you should define a class @code{FLOAT_OR_GENERAL_REGS} -which includes both of them. Otherwise you will get suboptimal code. +which includes both of them. Otherwise you will get suboptimal code, +or even internal compiler errors when reload cannot find a register in the +the class computed via @code{reg_class_subunion}. You must also specify certain redundant information about the register classes: for each class, which classes contain it and which ones are |