On Fri, Jul 6, 2018 at 5:20 PM, Andreas Krebbel wrote:
> On 06/20/2018 01:41 PM, Andreas Krebbel wrote:
>> When turning a user-defined numerical literal into an operator
>> invocation the literal needs to be translated to the execution
>> character set.
>>
>> Bootstrapped and regtested on s390x. x
On 06/20/2018 01:41 PM, Andreas Krebbel wrote:
> When turning a user-defined numerical literal into an operator
> invocation the literal needs to be translated to the execution
> character set.
>
> Bootstrapped and regtested on s390x. x86_64 still running.
> Ok to apply if x86_64 is clean?
>
> By
On 06/26/2018 11:17 AM, Rainer Orth wrote:
> Hi Andreas,
>
>> When turning a user-defined numerical literal into an operator
>> invocation the literal needs to be translated to the execution
>> character set.
>>
>> Bootstrapped and regtested on s390x. x86_64 still running.
>> Ok to apply if x86_64
Hi Andreas,
> When turning a user-defined numerical literal into an operator
> invocation the literal needs to be translated to the execution
> character set.
>
> Bootstrapped and regtested on s390x. x86_64 still running.
> Ok to apply if x86_64 is clean?
the new testcase FAILs on Solaris
FAIL:
On Wed, Jun 20, 2018 at 7:41 AM, Andreas Krebbel
wrote:
> When turning a user-defined numerical literal into an operator
> invocation the literal needs to be translated to the execution
> character set.
>
> Bootstrapped and regtested on s390x. x86_64 still running.
> Ok to apply if x86_64 is clean
When turning a user-defined numerical literal into an operator
invocation the literal needs to be translated to the execution
character set.
Bootstrapped and regtested on s390x. x86_64 still running.
Ok to apply if x86_64 is clean?
Bye,
-Andreas-
gcc/cp/ChangeLog:
2018-06-20 Andreas Krebbel