search for: reportspam

...Тема: Re: RFC: Add a preprocessor to yaml2obj (and other YAML tools) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. If you suspect potential phishing or spam email, report it to ReportSpam at accesssoftek.com As someone who suggested this kind of functionality in a review earlier, this will certainly be useful, I think. I think the syntax makes sense to me, if we allow for unrecognised macros to just be treated as part of the input string. This means we don't have to worry about...

Hi Ivan, On 2019-01-18 10:15, Ivan Kosarev wrote: > IIRC, there were proposals/attempts to represent accesses to array > elements as accesses to their first elements, which can technically be > encoded with the current TBAA format and thus may work as an > incremental improvement on top of the existing TBAA machinery you are > looking for. But this may need making sure there

...19 16:02, Jonas Paulsson wrote: >> CAUTION: This email originated from outside of the organization. Do >> not click links or open attachments unless you recognize the sender >> and know the content is safe.  If you suspect potential phishing or >> spam email, report it to ReportSpam at accesssoftek.com >> >> Hi Ivan, >> >> >> On 2019-01-18 10:15, Ivan Kosarev wrote: >>> IIRC, there were proposals/attempts to represent accesses to array >>> elements as accesses to their first elements, which can technically be >>> encoded...

...-dev] preferred way to return expected values > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. If you suspect potential phishing or spam email, > report it to ReportSpam at accesssoftek.com > Many thanks for the reply, > right, this is what the discussion is about. > > > On Mon, Sep 28, 2020 at 10:57 AM David Blaikie <dblaikie at gmail.com> wrote: > >> To clarify, this is a discussion around whether given some move-only type >> X...

...dev] Simulation of load-store forwarding with MI scheduler on AArch64 CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. If you suspect potential phishing or spam email, report it to ReportSpam at accesssoftek.com On Sep 14, 2020, at 9:40 AM, Evgeny Leviant via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: Hi list, Is it possible to simulate load to store forwarding on aarch64 with MI scheduling model on AArch64? For instance $x0 data late...

...to return expected values >> >> CAUTION: This email originated from outside of the organization. Do not >> click links or open attachments unless you recognize the sender and know >> the content is safe. If you suspect potential phishing or spam email, >> report it to ReportSpam at accesssoftek.com >> Many thanks for the reply, >> right, this is what the discussion is about. >> >> >> On Mon, Sep 28, 2020 at 10:57 AM David Blaikie <dblaikie at gmail.com> >> wrote: >> >>> To clarify, this is a discussion around whether...

Many thanks for the reply, right, this is what the discussion is about. On Mon, Sep 28, 2020 at 10:57 AM David Blaikie <dblaikie at gmail.com> wrote: > To clarify, this is a discussion around whether given some move-only type > X, implicitly convertible to Y and the code "Y func() { X x; return x; }" > is that valid in LLVM? (and, as a corollary, if the type isn't

On Fri, 21 Jun 2019 at 13:05, Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I think Geroge (cc'ed) knows better than me in that area. > > lld is underdocumented, and in particular there is virtually no documentation about its linker script support. Our basic strategy is to follow the GNU's documentation and the implementations unless it is too hard or

...tat.ethz.ch/pipermail/r-devel/2024-March/083302.html ------------------------------------ This email has been scanned for spam & viruses. If you believe this email should have been stopped by our filters, click the following link to report it (https://portal-uk.mailanyone.net/index.html#/outer/reportspam?token=dXNlcj1zaW1vbi5hbmRyZXdzQGJhYnJhaGFtLmFjLnVrO3RzPTE3MTUxOTUxMjQ7dXVpZD02NjNCQ0NGMzA1RDJGMzA3RDhDMjIxQTZCRUE3MEQ3MDt0b2tlbj0yZTdkOWY0ZjNjZmQ2NGQyZGFlMmYwZjQ2MTk5NjdmODk2ZDM3YjQyOw%3D%3D).

...alues >>> >>> CAUTION: This email originated from outside of the organization. Do not >>> click links or open attachments unless you recognize the sender and know >>> the content is safe. If you suspect potential phishing or spam email, >>> report it to ReportSpam at accesssoftek.com >>> Many thanks for the reply, >>> right, this is what the discussion is about. >>> >>> >>> On Mon, Sep 28, 2020 at 10:57 AM David Blaikie <dblaikie at gmail.com> >>> wrote: >>> >>>> To clarify, thi...

? Wed, 8 May 2024 16:59:25 +0000 Simon Andrews <simon.andrews at babraham.ac.uk> ?????: > The lapack libraries are: > > $ rpm -qa | grep lapack > lapack-3.9.0-10.el9.x86_64 > lapack64_-3.9.0-10.el9.x86_64 > lapack64-3.9.0-10.el9.x86_64 > lapack-devel-3.9.0-10.el9.x86_64 Thanks for this information! I figured out I needed to enable the "PowerTools/CRB" repo,

Hi, I'm in the process of migrating from clang5 to clang10. Unfortunately clang10 introduced a negative performance impact. The cause is an increase of PLT entries from this patch (first released in clang7): https://bugs.llvm.org/show_bug.cgi?id=36370 https://reviews.llvm.org/D43383 If I revert that clang patch locally, the additional PLT entries and the performance impact disappear. This

...19 15:57, Jonas Paulsson wrote: >> CAUTION: This email originated from outside of the organization. Do >> not click links or open attachments unless you recognize the sender >> and know the content is safe.  If you suspect potential phishing or >> spam email, report it to ReportSpam at accesssoftek.com >> >> Hi, >> >> It was a while now since I first asked about TBAA, and I am now getting >> back to this, trying to understand TBAA as it seems that the issue I >> described earlier originally in this thread is still one of many "TODO&quot...

Hi list, Is it possible to simulate load to store forwarding on aarch64 with MI scheduling model on AArch64? For instance $x0 data latency in the example below should be 1 cycle ldr $x0, [$x1] str $x0, [$x2] But it should be 4 cycles if we have another instruction: ldr $x0, [$x1] add $x0, $x0, 4 For ALU instructions it’s possible to use either ReadAdvance or SchedReadAdvance, but I don’t see

Hi, It was a while now since I first asked about TBAA, and I am now getting back to this, trying to understand TBAA as it seems that the issue I described earlier originally in this thread is still one of many "TODO"s in CGExpr.cpp (http://lists.llvm.org/pipermail/llvm-dev/2018-September/126290.html). I would like to help on this to the best of my abilities, but I'm not quite

I am adding -D k=v to yaml2obj, similar to clang -D. This makes it easy to generate {32-bit,64-bit} x {big-endian,little-endian} tests. --- !ELF FileHeader: Class: ELFCLASS[[BITS]] Data: ELFDATA2[[ENCODE]] Type: ET_DYN Machine: EM_X86_64 # RUN: yaml2obj -D BITS=32 -D ENCODE=LSB %s -o %t.32le # RUN: yaml2obj -D BITS=32 -D ENCODE=MSB %s -o %t.32le # RUN: yaml2obj

...ormance impact when upgrading clang >>>> >>>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. If you suspect potential phishing or spam email, report it to ReportSpam at accesssoftek.com >>>> >>>> Hi, >>>> >>>> I'm in the process of migrating from clang5 to clang10. Unfortunately clang10 introduced a negative performance impact. The cause is an increase of PLT entries from this patch (first released in clang7...

Hi all, Many of our lit tests use FileCheck and a tool like llvm-readobj to check properties of a section header/symbol/etc. A typical (pseudoised for brevity) output to match against might be something like the following: Symbols [ Symbol { Name: foo Value: 0 Type: Function Section: .foo (1) } Symbol { Name: bar Value: 1 Type: Object Section: .foo (1) } ]

Please send any comments. As mentioned at the end I will follow up with some patches as soon as they are cleaned up and I create some test cases. RFC: Safe Whole Program Devirtualization Enablement =================================================== High Level Summary ------------------ The goal of the changes described in this RFC is to support aggressive Whole Program Devirtualization without