https://bugs.kde.org/show_bug.cgi?id=358620
--- Comment #12 from Julian Seward <jsew...@acm.org> ---
See https://bugs.kde.org/show_bug.cgi?id=322935#c27 and the
comments that follow.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374940
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Resolution|--- |INVALID
https://bugs.kde.org/show_bug.cgi?id=374940
--- Comment #7 from Julian Seward <jsew...@acm.org> ---
FWIW, the ppc32-elf ABI says
Data in the stack segment at addresses below the stack pointer
contain undefined values.
The ppc64-elf ABI says
As discussed later in this chapter, the
https://bugs.kde.org/show_bug.cgi?id=374940
--- Comment #6 from Julian Seward <jsew...@acm.org> ---
(In reply to Matthias Urlichs from comment #4)
> * the kernel needs to handle negative %esp offsets all the time because when
> you grow the stack the kernel "sees" th
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #8 from Julian Seward <jsew...@acm.org> ---
(In reply to Patrik Nyberg from comment #5)
Are you sure that the i5-6200U connection is the only thing in
common? That processor is a mid-range Skylake, and I am sure we
would have heard
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #4 from Julian Seward <jsew...@acm.org> ---
I don't have any such problems with the 4.9.3 kernel that comes
with Fedora 25. Is it possible that this is a Gentoo-specific
problem?
--
You are receiving this mail because:
You are wa
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #7 from Julian Seward <jsew...@acm.org> ---
(In reply to Patrik Nyberg from comment #6)
> This patch will solve the problem (at least for the simple hello world case).
Sure. That just disables the assertion, though. It doesn'
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #2 from Julian Seward <jsew...@acm.org> ---
(In reply to Patrik Nyberg from comment #1)
> Downgrading kernel to version 4.4.39-gentoo and the error is no longer
> present.
Yeah, I did wonder if this is kernel specific. The
https://bugs.kde.org/show_bug.cgi?id=344139
--- Comment #5 from Julian Seward <jsew...@acm.org> ---
> Created attachment 103551 [details]
> [PATCH 1/2] Initialize x86 system GDT on first use.
Committed, valgrind r16204.
> Created attachment 103552 [details]
> [PATCH 2/2] VEX
https://bugs.kde.org/show_bug.cgi?id=374850
--- Comment #5 from Julian Seward <jsew...@acm.org> ---
Oh, wait. This got discussed the other day. The conclusion is
that it is basically a kernel bug that only manifests on Skylake
processors. Are you running on Skylake?
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=344139
--- Comment #6 from Julian Seward <jsew...@acm.org> ---
Richard .. 2 years later .. can we close this now?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372120
--- Comment #2 from Julian Seward <jsew...@acm.org> ---
(In reply to Mark Wielaard from comment #1)
> Yeah, I think it would be a good idea to at least recognize the
> default (gnu_v3) style c++ mangling, which always starts with _Z.
>
https://bugs.kde.org/show_bug.cgi?id=371916
--- Comment #18 from Julian Seward <jsew...@acm.org> ---
Some comments on the v3 patch:
Mostly it looks fine. Below [1] some small comments.
Larger comments:
* I assume there are no regressions with correctness or performance
with thi
https://bugs.kde.org/show_bug.cgi?id=352767
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=348616
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #12 from Julian Seward <jsew...@acm.org> ---
Probably your least-worst option at this point is to compile the test
program in the configuration where the errors are not reported, and hope
that it all gets compiled into a single fu
https://bugs.kde.org/show_bug.cgi?id=369459
--- Comment #16 from Julian Seward <jsew...@acm.org> ---
I would be happy to make a generalised version of Maran's fixes,
so as to get arm{32,64} working on these cores. I don't really
want it to be the default implementation though, since w
https://bugs.kde.org/show_bug.cgi?id=372794
--- Comment #1 from Julian Seward <jsew...@acm.org> ---
Ach, the logic there that verifies whether the instruction decode is
valid, is wrong. Try this:
change
// Paranoia ..
vassert(szBlg2 <= 3);
if (szBlg2 < 3) { vasse
https://bugs.kde.org/show_bug.cgi?id=372358
--- Comment #2 from Julian Seward <jsew...@acm.org> ---
I can't reproduce this. Are you sure this is right? I tried
thusly:
int main ( void )
{
__asm__ __volatile__(
".byte 0xC5, 0xFA, 0x7F, 0x45, 0x80, 0xC5, 0xFA, 0x7F, 0x4D, 0x90
https://bugs.kde.org/show_bug.cgi?id=371989
--- Comment #4 from Julian Seward <jsew...@acm.org> ---
I'd fix this, if I could think of a sane way to do so. Alas ..
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372358
--- Comment #4 from Julian Seward <jsew...@acm.org> ---
Are you running this test on a machine whose CPUID says that AVX isn't
supported? Does the test actually run natively on the machine? I'm pretty
sure VEX will decline to decode th
https://bugs.kde.org/show_bug.cgi?id=372794
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=374940
--- Comment #3 from Julian Seward <jsew...@acm.org> ---
The libev code is incorrect and should be fixed. It it violates the ABI.
The problem isn't that the memory is uninitialised. It is that the
program isn't allowed to access below %esp at an
https://bugs.kde.org/show_bug.cgi?id=372794
--- Comment #5 from Julian Seward <jsew...@acm.org> ---
(In reply to Claus Strasburger from comment #4)
> more -- this one is 0xFEBB0B40, VRINTM.f64), in code generated with
> -mcpu=cortex-a53 -mfpu=neon-fp-armv8 (for the Raspberry Pi
https://bugs.kde.org/show_bug.cgi?id=372794
--- Comment #6 from Julian Seward <jsew...@acm.org> ---
> all the instructions that "gcc-5.4 -mfpu=neon-fp-armv8".
+= "generates."
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #23 from Julian Seward <jsew...@acm.org> ---
(In reply to Carl Ponder from comment #22)
> I know they're not zeroing out the space.
That doesn't sync with my understanding of the discussion above.
I think your chances o
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #21 from Julian Seward <jsew...@acm.org> ---
(In reply to Tom Hughes from comment #19)
My assumption about what __builtin_aa does is: it moves RSP down by the
specified amount, zeroes out the new area, and then returns. Except ..
ho
https://bugs.kde.org/show_bug.cgi?id=375839
--- Comment #7 from Julian Seward <jsew...@acm.org> ---
(In reply to Julian Seward from comment #1)
> VEX has a very poor (verbose) translation for such instructions [..]
VEX r3331 somewhat improves this, reducing the size of the gener
https://bugs.kde.org/show_bug.cgi?id=375839
--- Comment #8 from Julian Seward <jsew...@acm.org> ---
VEX r3335 further improves the situation a bit. I would be interested
to hear if this makes it possible to run these problematic cases without
the workaround in comment #4 (the use of --vex
https://bugs.kde.org/show_bug.cgi?id=358697
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=377698
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
CC||jsew...@acm.org
--- C
https://bugs.kde.org/show_bug.cgi?id=377698
--- Comment #7 from Julian Seward <jsew...@acm.org> ---
(In reply to Diane M from comment #6)
> I believe the if is necessary, because it is checking whether the function
> pointer is defined, [..]
Oh, you're right. I missed that.
r+ t
https://bugs.kde.org/show_bug.cgi?id=375839
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=375839
--- Comment #4 from Julian Seward <jsew...@acm.org> ---
I should add: as a workaround, you can try specifying
--vex-guest-max-insns=25
and if that still doesn't work, lowering the value towards zero.
You shouldn't go below about 10. Lower
https://bugs.kde.org/show_bug.cgi?id=375839
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
CC||rsbul...@gma
https://bugs.kde.org/show_bug.cgi?id=378068
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=377966
--- Comment #1 from Julian Seward <jsew...@acm.org> ---
(In reply to John Reiser from comment #0)
> instruction; it [allocates and] clears the cache line whose address
> corresponds to the contents of register x5.
Yes, ppc has something
https://bugs.kde.org/show_bug.cgi?id=303877
Bug 303877 depends on bug 377717, which changed state.
Bug 377717 Summary: Fix massive space leak when reading compressed debuginfo
sections
https://bugs.kde.org/show_bug.cgi?id=377717
What|Removed |Added
https://bugs.kde.org/show_bug.cgi?id=377717
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=377717
Bug ID: 377717
Summary: Fix massive space leak when reading compressed
debuginfo sections
Product: valgrind
Version: 3.13 SVN
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=303877
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Depends on||377717
Reference
https://bugs.kde.org/show_bug.cgi?id=377717
--- Comment #1 from Julian Seward <jsew...@acm.org> ---
Created attachment 104607
--> https://bugs.kde.org/attachment.cgi?id=104607=edit
Fix
A fix. Largely rewrites get_slowcase, documents abovementioned invariant,
and adds a bunch
https://bugs.kde.org/show_bug.cgi?id=375839
--- Comment #13 from Julian Seward <jsew...@acm.org> ---
(In reply to ux from comment #12)
> Thread 1: status = VgTs_Runnable (lwpid 5547)
> ==5547==at 0x5BF9BE: ff_vp9_idct_iadst_16x16_add_avx2 (vp9itxfm.asm:2149)
> ==5547==
https://bugs.kde.org/show_bug.cgi?id=375839
--- Comment #20 from Julian Seward <jsew...@acm.org> ---
(In reply to ux from comment #19)
> Seems to work, all our VP9 tests pass with this. Thanks!
Committed as vex r3346.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=375839
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Summary|Temporary storage exhusted |Temporary storage exh
https://bugs.kde.org/show_bug.cgi?id=375839
--- Comment #11 from Julian Seward <jsew...@acm.org> ---
Uh, I thought I fixed it pretty comprehensively in r3344. Anyway,
can you get me please a copy of the basic block that contains the
failing address?
at 0x
https://bugs.kde.org/show_bug.cgi?id=375839
--- Comment #16 from Julian Seward <jsew...@acm.org> ---
(In reply to ux from comment #15)
> My bad. So this block?
> Full function in attachment.
Ok .. nearly there. Could you please disassemble the function using the
normal AT syntax
https://bugs.kde.org/show_bug.cgi?id=375839
--- Comment #18 from Julian Seward <jsew...@acm.org> ---
Try this. Does it help?
Index: priv/guest_amd64_toIR.c
===
--- priv/guest_amd64_toIR.c (revision 3345)
++
https://bugs.kde.org/show_bug.cgi?id=378732
--- Comment #1 from Julian Seward <jsew...@acm.org> ---
Reuben!
Per Chet's last comment line
There's no place where that value is part of a data segment.
I think that's a misreading of V's (admittedly ambiguous) claim about
the segment. I
https://bugs.kde.org/show_bug.cgi?id=378732
--- Comment #5 from Julian Seward <jsew...@acm.org> ---
(In reply to rrt from comment #2)
> By default, bash seems to use its own malloc (and certainly in the case
> where I do a default "./configure && make" from git sour
https://bugs.kde.org/show_bug.cgi?id=344524
--- Comment #17 from Julian Seward <jsew...@acm.org> ---
Also, your implementation uses guest_state.LLaddr == 0 to mean "there
is no transaction in progress". So guest_state.LLaddr == 0 has a special
meaning that is different from
https://bugs.kde.org/show_bug.cgi?id=344524
--- Comment #18 from Julian Seward <jsew...@acm.org> ---
Actually, I'd prefer to have it so that any attempt to do StoreCond
will cause all following attempts to fail, up until a new LoadLinked
is done. How does that sound?
LoadLinke
https://bugs.kde.org/show_bug.cgi?id=344524
--- Comment #16 from Julian Seward <jsew...@acm.org> ---
(In reply to Maran Pakkirisamy from comment #8)
Maran,
I was studying this bug and your fix, so as to see how to apply it to ARM.
I have a question:
> With the update, only step 3 i
https://bugs.kde.org/show_bug.cgi?id=344524
--- Comment #19 from Julian Seward <jsew...@acm.org> ---
Hmm, even that is too relaxed, because it doesn't reject mismatched
load vs store sizes. Here's a variant that does check sizes, and
uses size == 0 to mean "no transaction pending&qu
https://bugs.kde.org/show_bug.cgi?id=370028
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
CC||jsew...@acm.org
--- C
https://bugs.kde.org/show_bug.cgi?id=373166
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
CC||jsew...@acm.org
--- C
https://bugs.kde.org/show_bug.cgi?id=344139
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=372185
--- Comment #2 from Julian Seward <jsew...@acm.org> ---
The current trunk supports ARMv8 32 bit instructions, almost
everything except conversions to/from 16-bit floats. Give it
a try.
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=372185
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=371503
--- Comment #1 from Julian Seward <jsew...@acm.org> ---
Does this still happen with the trunk? It has supported
"PRFM (register)" since 2015-08-16.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=371916
--- Comment #22 from Julian Seward <jsew...@acm.org> ---
Can this be closed now? In the NEWS file it is listed as being closed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372861
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
CC||m...@redhat.com
-
https://bugs.kde.org/show_bug.cgi?id=371668
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=376729
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
CC||will_schm...@vnet.i
https://bugs.kde.org/show_bug.cgi?id=372779
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Summary|valgrind will hang |valgrind will hang
https://bugs.kde.org/show_bug.cgi?id=372120
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=372182
Bug 372182 depends on bug 372120, which changed state.
Bug 372120 Summary: c++ demangler demangles symbols which are not c++
https://bugs.kde.org/show_bug.cgi?id=372120
What|Removed |Added
https://bugs.kde.org/show_bug.cgi?id=373990
--- Comment #1 from Julian Seward <jsew...@acm.org> ---
It's complaining about this
assign(scale, unop(Iop_I32UtoF64, mkU32( ((UInt)1) << (frac_bits-1) )));
in the case "VCVT fixed<->floating, VFP" (cond 1110 1D11 1p
https://bugs.kde.org/show_bug.cgi?id=375150
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=375839
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
CC||nagendra.g...@gma
https://bugs.kde.org/show_bug.cgi?id=375839
--- Comment #1 from Julian Seward <jsew...@acm.org> ---
Yes, VEX has a very poor (verbose) translation for such instructions
and generates huge amounts of code, which breaks the JIT. We should
fix this somehow.
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=374482
--- Comment #2 from Julian Seward <jsew...@acm.org> ---
This has been reported several times in the past couple of months.
It's (surprisingly) a kernel bug. I'll try to find the relevant bug report.
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=374482
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=375171
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
CC||rick.ramstetter+kde@g
https://bugs.kde.org/show_bug.cgi?id=375839
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
CC||nmanj...@pretaktova
https://bugs.kde.org/show_bug.cgi?id=375171
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Summary|Crash when running "hello |VG_(schedule
https://bugs.kde.org/show_bug.cgi?id=79362
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Attachment #68213|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=79362
--- Comment #65 from Julian Seward <jsew...@acm.org> ---
(In reply to Philippe Waroquiers from comment #63)
Thanks for the feedback. I'll fix the small stuff.
> * For execontext, instead of just storing the execcontext
> (e.g. in
https://bugs.kde.org/show_bug.cgi?id=79362
--- Comment #66 from Julian Seward <jsew...@acm.org> ---
(In reply to Philippe Waroquiers from comment #63)
Thanks for the feedback. I'll fix the small stuff.
> * For execontext, instead of just storing the execcontext
> (e.g. in
https://bugs.kde.org/show_bug.cgi?id=79362
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Attachment #107001|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=381553
--- Comment #18 from Julian Seward <jsew...@acm.org> ---
Created attachment 106492
--> https://bugs.kde.org/attachment.cgi?id=106492=edit
Use callee-saved registers in preference to caller-saved registers, if possible
This small change appli
https://bugs.kde.org/show_bug.cgi?id=381553
--- Comment #19 from Julian Seward <jsew...@acm.org> ---
Actual numbers:
r2
2,773 (60,618 -> 979,296; ratio 16.2) [0 scs] avg tce size 353
r3-before
2,767 (60,481 -> 1,047,119; ratio 17.3) [0 scs] avg tce size 378
r3-after
2,767 (60,48
https://bugs.kde.org/show_bug.cgi?id=381553
--- Comment #20 from Julian Seward <jsew...@acm.org> ---
For the actual cost of doing register allocation, for /usr/bin/date on
Memcheck,
I have the following profile results from Callgrind. These numbers are for
doRegisterAllocation_{v2,v3} a
https://bugs.kde.org/show_bug.cgi?id=381326
--- Comment #6 from Julian Seward <jsew...@acm.org> ---
In particular I am trying to figure out if this can somehow be used to avoid
the problems shown at
https://bugs.llvm.org//show_bug.cgi?id=12319
and
https://github.com/rust-lang/rust/issues
https://bugs.kde.org/show_bug.cgi?id=381326
--- Comment #5 from Julian Seward <jsew...@acm.org> ---
(In reply to John Reiser from comment #4)
Interesting, but I don't really understand it. What's the underlying insight
here? In particular, why is it the case that knowing the two op
https://bugs.kde.org/show_bug.cgi?id=79362
--- Comment #60 from Julian Seward <jsew...@acm.org> ---
(In reply to Julian Seward from comment #59)
> AFAICS, the only thing that you can conclude from the fact that
>
> execontext1.ecu > execontext2.ecu
>
> is that execonte
https://bugs.kde.org/show_bug.cgi?id=79362
--- Comment #59 from Julian Seward <jsew...@acm.org> ---
(In reply to Howard Chu from comment #57)
> a clean fix has been available for nearly 5 years.
I'm trying to understand the proposed fix. What I've gathered is:
(1) Each ExeContext has
https://bugs.kde.org/show_bug.cgi?id=381553
--- Comment #15 from Julian Seward <jsew...@acm.org> ---
I think it's done (in a stupid way) using the has_hlrs hint boolean and the
loop beginning at host_generic_reg_alloc2.c:1367 (after applying the patch).
If the code contains any calls
https://bugs.kde.org/show_bug.cgi?id=381553
--- Comment #16 from Julian Seward <jsew...@acm.org> ---
(In reply to Julian Seward from comment #15)
> loop beginning at host_generic_reg_alloc2.c:1367 (after applying the patch).
Sorry, line 1367 in the unpatched sources.
--
You are
https://bugs.kde.org/show_bug.cgi?id=381553
--- Comment #14 from Julian Seward <jsew...@acm.org> ---
(In reply to Ivo Raisr from comment #13)
> Patches 005 implement function find_vreg_to_spill().
That's excellent. With this in place, I can start and quit Firefox on
Memcheck, which
https://bugs.kde.org/show_bug.cgi?id=369459
--- Comment #17 from Julian Seward <jsew...@acm.org> ---
Fixed. It appears to work, to the extent that I can actually test it
without access to the hardware in question. r3352, r16309. Use
--sim-hints=fallback-llsc to use the alter
https://bugs.kde.org/show_bug.cgi?id=369459
--- Comment #18 from Julian Seward <jsew...@acm.org> ---
(In reply to Julian Seward from comment #17)
> Fixed. [..]
Andrew, can you test the fix, please?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365327
--- Comment #14 from Julian Seward <jsew...@acm.org> ---
(In reply to Louis Brunner from comment #12)
Louis, thanks for working on this. A question: with your patch applied,
does it still work on earlier MacOS versions (10.11, 10.10) ?
-
https://bugs.kde.org/show_bug.cgi?id=79362
--- Comment #75 from Julian Seward <jsew...@acm.org> ---
(In reply to Philippe Waroquiers from comment #73)
Thank you for redoing the measurements.
> With this, the scan is slower : for big applications (260_000 EC,
> 6_300_000 IP),
https://bugs.kde.org/show_bug.cgi?id=381553
--- Comment #44 from Julian Seward <jsew...@acm.org> ---
010 works OK on arm64-linux. On arm(32)-linux, it fails at startup
verifying sanity of the register set, due to a small error in the
definition of getRRegUniverse_ARM: the first allocab
https://bugs.kde.org/show_bug.cgi?id=79362
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Attachment #106984|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=383275
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
CC||jsew...@acm.org
--- C
https://bugs.kde.org/show_bug.cgi?id=79362
--- Comment #72 from Julian Seward <jsew...@acm.org> ---
(In reply to Philippe Waroquiers from comment #71)
> Created attachment 107073 [details]
> (hack) : patch that adds measurement code to scan the EC for a .so unload
+for (j
https://bugs.kde.org/show_bug.cgi?id=383010
--- Comment #1 from Julian Seward <jsew...@acm.org> ---
This is a quite good start. Here are some initial comments. This isn't a
full review but should give you some initial feedback.
--
+// AVX-512 - use a real
https://bugs.kde.org/show_bug.cgi?id=368868
Julian Seward <jsew...@acm.org> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
1 - 100 of 891 matches
Mail list logo
