> On Jan 19, 2018, at 3:58 PM, Segher Boessenkool <seg...@kernel.crashing.org>
> wrote:
>
> On Fri, Jan 19, 2018 at 10:20:23PM +0100, Andreas Schwab wrote:
>> On Jan 19 2018, Bill Schmidt <wschm...@linux.vnet.ibm.com> wrote:
>>
>>>> On Jan 19, 2018, at 3:09 PM, Jakub Jelinek <ja...@redhat.com> wrote:
>>>>
>>>> On Fri, Jan 19, 2018 at 02:58:07PM -0600, Bill Schmidt wrote:
>>>>> --- gcc/testsuite/gcc.target/powerpc/safe-indirect-jump-2.c
>>>>> (revision 256894)
>>>>> +++ gcc/testsuite/gcc.target/powerpc/safe-indirect-jump-2.c
>>>>> (working copy)
>>>>> @@ -30,4 +30,4 @@ int foo (int x)
>>>>>
>>>>> /* { dg-final { scan-assembler "crset 30" } } */
>>>>> /* { dg-final { scan-assembler "beqctr- 7" } } */
>>>>> -/* { dg-final { scan-assembler "b ." } } */
>>>>> +/* { dg-final { scan-assembler "b $" } } */
>>>>
>>>> Does $ in scan-assembler really match a literal $ and not end of line?
>>>> Looking around, most of scan-assembler patterns that want to match a $ use
>>>> \\\$
>>>
>>> Right. Working on getting the right number of backslashes in here...
>>> I can never remember which ones need one and which need 3.
>>
>> Use braces.
>
> Yes, either
>
> +/* { dg-final { scan-assembler "b \\\$" } } */
>
> or (preferably)
>
> +/* { dg-final { scan-assembler {b \$} } } */
Thanks, going with the latter suggestion. My environment crapped out so I'm
restarting
the regstrap. Will repost later this evening after it passes.
Thanks,
Bill
>
>
> Segher
