On 05/07/2017 17:24, Martin Sebor wrote:
[*] While the example (copied below) is valid, accessing the object
after someFunction() has returned via a reference or pointer to it
is not.
void somefunction(const Object& object);
{
void* p = &object;
object.~Object();
new(p) Obj
I see large numbers of timeouts in Ada tests on trunk in parallel
run s (make -j96) on x86_64. Messages like the one below appear
in the logs, suggesting some sort of heap corruption. I'm having
trouble reproducing it outside the rest of the test suite (i.e.,
by just running the Ada tests by the
> I see large numbers of timeouts in Ada tests on trunk in parallel
> run s (make -j96) on x86_64. Messages like the one below appear
> in the logs, suggesting some sort of heap corruption. I'm having
> trouble reproducing it outside the rest of the test suite (i.e.,
> by just running the Ada tes
On 7/7/2017 17:38, Eric Botcazou wrote:
I see large numbers of timeouts in Ada tests on trunk in parallel
run s (make -j96) on x86_64. Messages like the one below appear
in the logs, suggesting some sort of heap corruption. I'm having
trouble reproducing it outside the rest of the test suite (i
Hi,
Curious about this codegen:
- https://godbolt.org/g/5XxP5S
Why does gcc branch on _Bool, but emits a conditional move for an integer? can
it emit cmovne instead of branching? also curious where one would change this
to learn about GCC internals.
It’s not a bug, but it is a performance iss
