# HG changeset patch # User William Astle # Date 1458869114 21600 # Node ID 8222f30a0781c2b33c48bc7db6369edd831d51f4 # Parent 40de99bde5e015405c5cd746911807d1e70ef505 Commit the *correct* note about the gcc6809 code generation bug. diff -r 40de99bde5e0 -r 8222f30a0781 extra/README --- a/extra/README Thu Mar 24 19:08:25 2016 -0600 +++ b/extra/README Thu Mar 24 19:25:14 2016 -0600 @@ -98,13 +98,12 @@ There is one known code generation bug with current versions of gcc6809. If you are getting bad behaviour for some reason and are using optimization -(-O1 or higher, -Os), you may be hitting this bug. Adding "-fno-tree-ter" -after the "-O" options is known to correct this behaviour in some cases. If -someone who understands the gcc code is willing to look at it, patches for -the patch would be welcome (especially if that patch moves the base gcc -version upward). It is not clear whether this is a bug in the m6809 specific -code or the gcc core though it seems like it's in the gcc core. - +(-O1 or higher, -Os), you may be hitting this bug. If someone who +understands the gcc code is willing to look at it, patches for the patch +would be welcome (especially if that patch moves the base gcc version +upward). It is not clear whether this is a bug in the m6809 specific code +or the gcc core though it seems like it's in the gcc core. Disabling +optimization completely seems to generate correct, if suboptimal, code. NOTES ABOUT SPECIFIC PATCHES ============================