search for: snider

...ntroducing the constraint via the qualifier field might work. All, The volatile qualifier on an asm statement already indicates that the statement should be assumed to have side effects. Could we extend the functionality of volatile to also mean the asm statement is not duplicable? ~ Todd From: Snider, Todd Sent: Wednesday, February 13, 2019 11:40 AM To: 'paul.robinson at sony.com'; efriedma at quicinc.com Cc: llvm-dev at lists.llvm.org Subject: RE: [llvm-dev] [RFC] Potential extension to asm statement functionality The proposed "lbl" constraint below: __asm __volatile__ (...

...s loaded into their debug and test framework, the labels will cause breakpoints to be set at strategic points where they can query the state of the processor that the application is running on. ~ Todd From: Eli Friedman [mailto:efriedma at quicinc.com] Sent: Tuesday, February 12, 2019 1:36 PM To: Snider, Todd; llvm-dev at lists.llvm.org Subject: [EXTERNAL] RE: [llvm-dev] [RFC] Potential extension to asm statement functionality Can you go into a bit more detail about why someone would want to do this, as opposed to just writing a file scope inline asm, or a separate file in assembly? I can't...

Could this issue also be related to an “AphrontQueryException #1030: Got error 28 from storage engine” error when browsing Phabricator? ~ Todd Snider From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Hubert Tong via llvm-dev Sent: Friday, May 1, 2020 9:15 AM To: Mircea Trofin Cc: Nicolai Hähnle via llvm-dev Subject: [EXTERNAL] Re: [llvm-dev] arc diff says "disk is full"? It's still down. On Fri, May 1, 202...

*From: *Snider, Todd <t-snider at ti.com> *Date: *Thu, May 9, 2019 at 3:53 AM *To: *Rui Ueyama, James Y Knight *Cc: *llvm-dev > > James, Rui, > > > > If we are only talking about addressable hardware registers, peripherals, > etc., then the absolute address symbol is one way to facili...

...alogous ATTR_KIND identifiers in the AtttrKind enum, yet the ARM-specific CMSE_NS_CALL and CMSE_NS_ENTRY occupy slots in the AttrKind enum. Can someone point me to an example of a target-dependent attribute represented in the LLVM IR that does not occupy a slot in the AttrKind enum? Thanks, Todd Snider -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190314/008103e0/attachment.html>

....data or .bss) or a function at a fixed memory address, that's not something you can do with absolute symbols (but you can do with linker scripts), but is this what you really want? *From: *James Y Knight via llvm-dev <llvm-dev at lists.llvm.org> *Date: *Tue, May 7, 2019 at 2:39 AM *To: *Snider, Todd *Cc: *llvm-dev I don't think it's a "trick" at all -- it's just a definition of the symbol > at an absolute address. That's what absolute symbols are for. (You can also > use ".size sym, 4" ".type sym, object", if you want to let the linker...

...his part of the DwarfUnit::constructTypeDIe() function (circa line 958 in DwarfUnit.cpp) should be guarded with a target- or vendor-specific conditional if it is needed for a particular purpose. Otherwise, I propose that it be removed since it breaks compliance with the DWARF specification. ~ Todd Snider -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190730/1e12d07c/attachment.html>

...ctual data object (whether it be initialized or not) or function, where the symbol is defined in a section containing the definition of the data object or function, is a useful feature for customers. ~ Todd From: James Y Knight [mailto:jyknight at google.com] Sent: Friday, May 3, 2019 4:35 PM To: Snider, Todd; Peter Smith; Finkel, Hal J.; llvm-dev Subject: Re: [llvm-dev] [EXTERNAL] Re: RFC - a proposal to support additional symbol metadata in ELF object files in the ARM compiler It should result in an object file with a global absolute symbol. E.g. (here I'm building on x86-64 linux): $ echo...

> -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of > Adrian Prantl via llvm-dev > Sent: Friday, January 18, 2019 5:20 PM > To: Snider, Todd > Cc: llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] Potential DWARF debug info bug: DW_TAG_label DIE > has a DW_AT_prototyped attribute > > > > > On Jan 18, 2019, at 1:06 PM, Snider, Todd via llvm-dev <llvm- > dev at lists.llvm.org> wrote: > >...

...is that if the symbol is associated with a common data object, then the location attribute ends up being applied to the definition that the common symbol resolves to. ~ Todd -----Original Message----- From: Peter Smith [mailto:peter.smith at linaro.org] Sent: Tuesday, April 30, 2019 10:51 AM To: Snider, Todd Cc: llvm-dev Subject: [EXTERNAL] Re: [llvm-dev] RFC - a proposal to support additional symbol metadata in ELF object files in the ARM compiler On Tue, 30 Apr 2019 at 16:17, Snider, Todd via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > Hello All, > > > >...

...;strict DWARF" mode, and used only those tags, attributes, and combinations that are explicitly described in a given DWARF version. LLVM does not have such a mode, and the DWARF specification does not require it. --paulr From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Snider, Todd via llvm-dev Sent: Tuesday, July 30, 2019 12:59 PM To: llvm-dev Subject: Re: [llvm-dev] Invalid DW_AT_calling_convention generated for a DW_TAG_class_type I see now that this is a DWARF 5 addition. It is still invalid for DWARF 4 or earlier. From: llvm-dev [mailto:llvm-dev-bounces at lists....

On Wed, 1 May 2019 at 15:03, Finkel, Hal J. <hfinkel at anl.gov> wrote: > > On 5/1/19 7:22 AM, Christof Douma via llvm-dev wrote: > > Hi Snider. > > > > As you and Peter mentioned there are indeed toolchains that allow location placement from within the C/C++ source code, using attributes or similar. I always wonder if such extension is worth the effort. There are downsides like the non-standard ways of communicating this infor...

...ould tell the compiler to mark the asm statement as isNotDuplicable when an INLINEASM record is created to represent it There are alternatives to using an asm statement for this purpose, but I wondered if such an extension would be useful/valuable to the wider community. Thoughts? Opinions? Todd Snider Compiler Group Texas Instruments Incorporated -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190212/8b9dc069/attachment.html>

...est/MC/MachO/gen-dwarf.s). Does the DW_AT_prototyped attribute sever any purpose or provide any value in the context of a DW_TAG_label DIE? If not, I propose to remove the call to EmitAbbrev() on behalf of the DW_AT_prototyped attribute for a DW_TAG_label in EmitGenDwarfAbbrev(). Thoughts? Todd Snider Compiler Group Texas Instruments Incorporated Sugar Land, TX -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190118/12f81aac/attachment.html>

...= %0 call void @f2() unreachable 4: ; preds = %0 ret void } If the call to f2() is the only thing in the if block, then inserting an unreachable after it will later be interpreted as an unreachable block. Is this a legal optimization? ~ Todd Snider -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190604/b85beb49/attachment.html>

...attribute value - a value that is appropriate for the specified attribute kind Thoughts? Comments? Concerns? The anticipated next steps would be to add support for the location attribute and update the ARM/ELF LLVM back-end to support encoding the used attribute with the new mechanism. ~ Todd Snider Code Generation Tools Group Texas Instruments Incorporated -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190430/93f0b238/attachment-0001.html>

Hi Snider. As you and Peter mentioned there are indeed toolchains that allow location placement from within the C/C++ source code, using attributes or similar. I always wonder if such extension is worth the effort. There are downsides like the non-standard ways of communicating this information to the linke...

...= cn=Manager,dc= mydomain,dc=com ldap ssl = no utmp = Yes remote announce = 192.168.0.0 [homes] comment = Home Directories valid users = %U read only = No create mask = 0640 browseable = No [netlogon] comment = Network Logon Service path = /samba/netlogon guest ok = Yes Thanks, Chris Snider

Hi everyone ! I just wanna say that I can't configure Samba 3.0.3 to compile with LDAP Support ( --with-ldap ) Here's the log : checking for LDAP support... yes checking ldap.h usability... no checking ldap.h presence... no checking for ldap.h... no checking lber.h usability... no checking lber.h presence... no checking for lber.h... no configure: error: ldap.h is needed for LDAP

There are two 64-bit bitmasks maintained in AttributeImpl.h<https://sdocc.itg.ti.com/ui#file:review=11893/version=393846>: - AvailableFunctionAttrs is part of the AttributeListImpl class, and - AvailableAttrs is part of the AttributeSetNode class Both of these assume that the number of available enum attributes is limited to 64. In fact, a static_assert in