Michael Collison <michael.colli...@linaro.org> writes: > On 09/14/2015 02:34 AM, Richard Sandiford wrote: >> Michael Collison <michael.colli...@linaro.org> writes: >>> Here is a modified patch that takes your comments into account. Breaking >>> on depth == 0 with '>' does not work due to the code looking for whitespace. >> What goes wrong? Just to make sure we're talking about the same thing, >> I meant that in: >> >> (match_operand:FOO> ... >> >> the name should be "FOO" and you should get an error on ">" when parsing >> the text after the name, just like you would for: >> >> (match_operand:FOO] ... > > When I try breaking on '>' with a nesting depth of 0 all examples of > <FOO> fail.
I meant break when depth == 0 before the decrement that's associated with '>'. I think that problem would only occur if you broke _after_ decrementing the depth. >> It's not a big deal though, so... >> >>> 2015-08-25 Michael Collison <michael.colli...@linaro.org> >>> >>> PR other/57195 >>> * read-md.c (read_name): Allow mode iterators inside angle >>> brackets in rtl expressions. >> OK, thanks. > Meaning okay to check the patch in? Yeah, it's OK to check in. Richard
