Am 01.03.19 um 10:43 schrieb Iain Buclaw:
On Sun, 24 Feb 2019 at 16:30, Johannes Pfau wrote:
Backport latest murmurhash version from upstream (2.084.1). Ran gdc testsuite
on X86_64 linux and got feedback on the bugzilla this really fixes the issue.
Raise a pull request with upstream (dmd-cxx
Committed as rev. 269341 on trunk.
On 03/02/19 16:17, Thomas Koenig wrote:
> Hi Harald,
>
>> Adding -Wsurprising as option to gfortran exercised a code path
>> that I hadn't seen when working on simplifications for the TRANSFER
>> intrinsic. While regtesting, I realized that one of the checks wa
Hi Harald,
Adding -Wsurprising as option to gfortran exercised a code path
that I hadn't seen when working on simplifications for the TRANSFER
intrinsic. While regtesting, I realized that one of the checks was
too strict when the MOLD argument was scalar and of size 0 and should
only apply to a
Hi Steve,
On Thu, Feb 28, 2019 at 09:14:48PM +0100, Thomas Koenig wrote:
the attached patch fixes a wrong-code bug for gfortran where pointers
were not marked as escaping. A C_PTR can be stashed away and reused
later (at least as long as the variable it points to remains active).
This is not
On Fri, Mar 01, 2019 at 04:14:33PM -0500, Jason Merrill wrote:
> > Note, this is just a partial fix for the PR, for the second part (making
> > struct S { void *a; int b; };
> > void foo (S);
> > ... foo ({.b = 1}) work), I'm afraid I don't really understand what the C++
> > standard wants to say i
