similar to: PATCH: clang/LLVM - Sparc - inline ASM with floating pointer registers

Hi Patrick, I do not see a problem with those patches --- apart from missing tests ;) Cheers, Arnaud On Mon, Mar 21, 2016 at 3:11 PM, Patrick Boettcher via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Hi lists, > > Sorry for cross-posting, but these two patches are of concern to clang > and llvm. > > I'm compiling C-code which includes inline assembler which looks

Your change looks almost correct. You need: - Test cases. - Add the new 'f' type to the documentation in LangRef.rst. - Check the type of the arg (f32, f64, or f128) to choose the right one of FPRegsRegClass, DFPRegsRegClass, QFPRegsRegClass. Then, please submit for review, per http://llvm.org/docs/DeveloperPolicy.html (Typically best to do so via Phabricator,

Hi, in section B.29. (Write State Register Instructions) of 'The SPARC Architecture Manual Version 8' it is said that the "The write state register instructions are delayed-write instructions." The Y-register is a state-register. Furthermore in the B.29-secion there is a programming note saying: MULScc, RDY, SDIV, SDIVcc, UDIV, and UDIVcc implicitly read the Y register.

Hello, some misc. cleanup patches for speexdsp, nothing big I'm not sure about how to submit patches, so this is a test balloon :) ultimately, I'd like to fix the FIXED_POINT issue, see http://lists.xiph.org/pipermail/speex-dev/2013-December/008465.html currently, I think the only way to find out how speexdsp has been compiled is to resample some bytes and observe the output; which is

This patch-series implements the ARB_viewport_array for nvc0 and does a little house-cleanig afterwords. V2: Add Release-Notes, mark this in GL3 as done for nvc0 Don't mark the scissors dirty when we don't need to do that Tobias Klausmann (3): nvc0: implement multiple viewports/scissors, enable ARB_viewport_array docs: update GL3.txt, relnotes: mark GL_ARB_viewport_array as done

Hello, I am currently trying to connect my Dovecot mail server to Microsoft's Azure-AD and use it as password and user database. I am using version 2.3.7.1. Using the Azure-AD as passdb already works. In this context I noticed that the scope implementation is not yet merged. Since I haven't found any hints for an OAuth2 userdb implementation yet, I wanted to ask if there are any plans

On Tue, Apr 15, 2014 at 12:33 PM, Peter Meerwald <pmeerw at pmeerw.net> wrote: > Signed-off-by: Peter Meerwald <pmeerw at pmeerw.net> > --- > libspeexdsp/resample.c | 14 +++++++------- > 1 file changed, 7 insertions(+), 7 deletions(-) > > diff --git a/libspeexdsp/resample.c b/libspeexdsp/resample.c > index e32ca45..a19b997 100644 > ---

This patch-series implements the ARB_viewport_array for nvc0 and does a little house-cleanig afterwords. Tobias Klausmann (3): nvc0: implement multiple viewports/scissors, enable ARB_viewport_array nvc0: mark scissor in nvc0_clear_{} nv50/ir: Remove NV50_SEMANTIC_VIEWPORTINDEX and its last consumer .../drivers/nouveau/codegen/nv50_ir_driver.h | 1 -

Hi, I intended to file this bug on Bugzilla, but I've received no response from llvm-admin in the 10 days since asking for a Bugzilla account. I've written 2 test functions in C that take in a float array x of size n and output float array f(x), where f is either fabsf or logf. The LLVM 3.9 auto-vectorization docs claim that both functions will be vectorized:

Functionally identical but much simpler. Should also better integrate with future layer/viewport changes/fixes. Cc: 10.1 <mesa-stable at lists.freedesktop.org> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Not *strictly* necessary in stable, but it will make backporting later fixes easier. No regressions in piglit. src/gallium/drivers/nouveau/nv50/nv50_program.c | 5

https://bugs.freedesktop.org/show_bug.cgi?id=91236 Bug ID: 91236 Summary: [NVC3] Passive DP to HDMI adapter cannot use pixel clocks greater than 165 MHz Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

+Tanya for the account issue. > On Oct 27, 2016, at 11:36 AM, Eric Martin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, > I intended to file this bug on Bugzilla, but I've received no response from llvm-admin in the 10 days since asking for a Bugzilla account. > > I've written 2 test functions in C that take in a float array x of size n and output

Below is some C code and its LLVM translation (using a recent rev). The compiler goes ahead and loads from x in main, but it seems clear that a constant propagation pass could have inferred that x is 0. In fact that is what happens if x is static, but in this case I cannot see how external linkage of x would invalidate that optimization. This is one of those optimizations that would not be

Eric, I apologize for any delay or confusion. From my records/list archives, I saw that Anton had created an account for you on Oct 17th and responded to your email to llvm-admin. I am not sure what happened after that point as I thought the account was done. I just confirmed there is an account for you in bugzilla, so you should be good to go if you reset your password. -Tanya > On Oct 27,

Hello, I have been gone for a while, finishing work on my Master's thesis... Now that I'm back I updated LLVM to the most recent version and found that my FP_ABS SelectionDAGNode type and code generation was now conflicting with the new FABS node type. I brought the rest of my local modifications in line with the FABS implementation, so here is my patch that includes sqrt, sin and cos

So Reid came across a case where the current strategy (dropping locations when they move across basic blocks) proves to be at odds with another precept we have: inlinable calls must have locations, so that if/when they are inlined the location can be accurately described (due to the nature of our IR representation of inlining, a location must be given for the call site so that the DIEs for the

Hi John, On Sat, 7 Mar 2009, John Regehr wrote: > Below is some C code and its LLVM translation (using a recent rev). The > compiler goes ahead and loads from x in main, but it seems clear that a > constant propagation pass could have inferred that x is 0. In fact that > is what happens if x is static, but in this case I cannot see how > external linkage of x would invalidate

Hi list, hi Talin, I'm working on a frontend to generate IR using the IRBuilder from LLVM. Now I want to add source-level-debuginfo and for that I would like to use the DebugInfoBuilder as it is taking some of the burderns. Unfortunately it does not take all of them, yet. As of today, even in SVN, it only can add a part of information needed. Of course I also need stoppoint, declare,

Hi, I am trying to use dovecot with my virtual-hosting setup. I have all users in LDAP like uid=user,dc=domain.tld,o=myorganization for the user with the mail-address user at domain.tld. This is also the username that user should use for login, but it is nowhere in the ldap-db in this form together, just user and domain at their own places. Is it possible to authenticate with

Fine by me :) On Wed, Jan 7, 2009 at 1:35 PM, Chris Lattner <clattner at apple.com> wrote: > > On Jan 7, 2009, at 3:22 AM, Patrick Boettcher wrote: > > > Hi list, > > hi Talin, > > > > I'm working on a frontend to generate IR using the IRBuilder from > > LLVM. > > > > Now I want to add source-level-debuginfo and for that I would like