Lena Olson efcd8ae024 ruby: fix and/or precedence in slicc ... The slicc compiler currently treats && and || with the same precedence. This is highly non-intuitive to people used to C, and was probably an error. This patch makes && bind tighter than ||. For example, previously: if (A || B && C) compiled to: if ((A || B) && C) With this patch, it compiles to: if (A || (B && C)) Change-Id: Idbbd5b50cc86a8d6601045adc14a253284d7b791 Signed-off-by: Lena Olson (leolson@google.com) Reviewed-on: https://gem5-review.googlesource.com/2168 Reviewed-by: Jason Lowe-Power <jason@lowepower.com> Reviewed-by: Joe Gross <criusx@gmail.com> Reviewed-by: Sooraj Puthoor <puthoorsooraj@gmail.com> Maintainer: Jason Lowe-Power <jason@lowepower.com> [ Rebased onto master ] Signed-off-by: Andreas Sandberg <andreas.sandberg@arm.com>		2017-03-01 11:58:37 +00:00
..
ast	style: remove trailing whitespace	2016-02-06 17:21:18 -08:00
generate	slicc: Change the code generation so that the generated code is easier to read	2010-03-12 18:42:56 -08:00
symbols	style: [patch 1/22] use /r/3648/ to reorganize includes	2016-11-09 14:27:37 -06:00
__init__.py	slicc: Pure python implementation of slicc.	2009-09-22 18:12:39 -07:00
main.py	slicc: add a protocol statement and an include statement	2011-07-05 18:30:05 -07:00
parser.py	ruby: fix and/or precedence in slicc	2017-03-01 11:58:37 +00:00
util.py	slicc: cleanup slicc code and make it less verbose	2011-07-05 18:30:05 -07:00