On 3/29/19 5:37 PM, Marek Polacek wrote:
On Fri, Mar 29, 2019 at 05:29:27PM -0400, Jason Merrill wrote:
On 3/29/19 4:25 PM, Marek Polacek wrote:
On Thu, Mar 28, 2019 at 02:55:55PM -0400, Jason Merrill wrote:
On 3/27/19 5:45 PM, Marek Polacek wrote:
Here we have a non-dependent constructor in
Hi,
The patch merges the D front-end implementation with dmd upstream 5dd3eccc3.
Aligns the test flags between gcc and upstream, after adding support
to gdc-test.exp to handle extra source and file settings being passed
multiple times.
Regression tested on x86_64-linux-gnu.
Committed to trunk a
This fixes both callers in tsubst_requires_expr to
tsubst_constraint_variables to wrap their respective
trees in PARM_CONSTR_PARMS. This is to get the correct
parmeter constraints from the tree before calling
tsubst_constraint_variables like other callers
in constraint.cc and to avoid subtle bugs i
Hi Paul,
> While I was about it, I committed the fix for PR89841 with the fix for
> PR89842. The latter is even safer than the former.
This also fixes PR89844.
Thanks,
Dominique
This patch makes assignments correct, because they need to
match indices instead of types. In addition, we cut down the
codegen size. The symbols are longer than before, the the amount
of them is roughly the same, so there's no longer an explosion
in their amount.
Relops are the last bit in these
Hi Steve,
Sorry about the delay. Daytime stuff caught up with me.
While I was about it, I committed the fix for PR89841 with the fix for
PR89842. The latter is even safer than the former.
Committed as revision 270037.
Thanks
Paul
2019-03-30 Paul Thomas
PR fortran/89841
* trans-exp
My fix five years ago for PR 60241 was incomplete: when we reassign implicit
instances of a partial instantiation of a member template to the explicit
specialization of that partial instantiation, we also need to adjust the
CLASSTYPE_TI_ARGS to match what we'd get when looking up that instance afte
Hi Paul,
Bootstrapped and regtested on FC29/x86_64 - OK for trunk?
OK - looks obvious enough, and, IMO, is quite unlikely to cause
a regressions.
Thanks for the patch!
Regards
Thomas
On Sat, 30 Mar 2019 at 11:56, Eric Botcazou wrote:
>
> Tested on x86_64-pc-mingw32, OK for the mainline?
OK, thanks.
This patch is pretty self-explanatory. I have checked that a sensible
errors are given if 'exfunc' in the testcase is referenced if it is a
variable.
Bootstrapped and regtested on FC29/x86_64 - OK for trunk?
Paul
2019-03-30 Paul Thomas
PR fortran/87127
* resolve.c (check_host_associa
On 3/30/19 4:21 AM, Uros Bizjak wrote:
> On 3/29/19, Jeff Law wrote:
>> On 3/29/19 1:44 PM, Jakub Jelinek wrote:
>>> Hi!
>>>
>>> f{char,short,int,long}minus use a RMW instead of direct memory operation
>>> (regression from 8.3) on ia32. The problem is an extra register copy,
>>> which
>>> regcpro
Tested on x86_64-pc-mingw32, OK for the mainline?
2019-03-30 Eric Botcazou
* src/c++17/fs_ops.cc (fs::permissions): Use std::errc::not_supported.
--
Eric Botcazoudiff --git libstdc++-v3/src/c++17/fs_ops.cc libstdc++-v3/src/c++17/fs_ops.cc
index 3ff0ded1c66..5ca523826cb 100644
--- li
On 3/29/19, Jeff Law wrote:
> On 3/29/19 1:44 PM, Jakub Jelinek wrote:
>> Hi!
>>
>> f{char,short,int,long}minus use a RMW instead of direct memory operation
>> (regression from 8.3) on ia32. The problem is an extra register copy,
>> which
>> regcprop would fix up, but unfortunately peephole2 runs
13 matches
Mail list logo