Mercurial > hg > index.cgi

comparison extra/README @ 415:8222f30a0781

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Commit the *correct* note about the gcc6809 code generation bug.
author William Astle <lost@l-w.ca>
date Thu, 24 Mar 2016 19:25:14 -0600
parents 40de99bde5e0
children b4d0eafc5bfe
comparison
equal deleted inserted replaced
414:40de99bde5e0 415:8222f30a0781
96 NOTES ABOUT GCC6809 96 NOTES ABOUT GCC6809
97 =================== 97 ===================
98 98
99 There is one known code generation bug with current versions of gcc6809. If 99 There is one known code generation bug with current versions of gcc6809. If
100 you are getting bad behaviour for some reason and are using optimization 100 you are getting bad behaviour for some reason and are using optimization
101 (-O1 or higher, -Os), you may be hitting this bug. Adding "-fno-tree-ter" 101 (-O1 or higher, -Os), you may be hitting this bug. If someone who
102 after the "-O" options is known to correct this behaviour in some cases. If 102 understands the gcc code is willing to look at it, patches for the patch
103 someone who understands the gcc code is willing to look at it, patches for 103 would be welcome (especially if that patch moves the base gcc version
104 the patch would be welcome (especially if that patch moves the base gcc 104 upward). It is not clear whether this is a bug in the m6809 specific code
105 version upward). It is not clear whether this is a bug in the m6809 specific 105 or the gcc core though it seems like it's in the gcc core. Disabling
106 code or the gcc core though it seems like it's in the gcc core. 106 optimization completely seems to generate correct, if suboptimal, code.
107
108 107
109 NOTES ABOUT SPECIFIC PATCHES 108 NOTES ABOUT SPECIFIC PATCHES
110 ============================ 109 ============================
111 110
112 gcc6809lw-4.6.4-2.patch 111 gcc6809lw-4.6.4-2.patch