search for: subranges

Hi, ctfconvert is particularly unhappy about that (e.g., ERROR: ctfconvert: die 141: base type without name). Is it intended behavior? Simple testcase: int main(void) { int i[2]; return 0; } dwarfdump output: clang version 3.0 (tags/RELEASE_30/final): [...] LOCAL_SYMBOLS: [...] <3>< 120> DW_TAG_variable DW_AT_name i

Hi, ctfconvert is particularly unhappy about that (e.g., ERROR: ctfconvert: die 141: base type without name). Is it intended behavior? Simple testcase: int main(void) { int i[2]; return 0; } dwarfdump output: clang version 3.0 (tags/RELEASE_30/final): [...] LOCAL_SYMBOLS: [...] <3>< 120> DW_TAG_variable DW_AT_name i

On Feb 11, 2012, at 7:51 AM, Yuri Pankov <yuri.pankov at gmail.com> wrote: > Hi, > > ctfconvert is particularly unhappy about that (e.g., ERROR: ctfconvert: > die 141: base type without name). Is it intended behavior? Not that I know of, please file a bug. Thanks! -eric

Hi, I'm stuck trying to fix a variety of problems that occur with undef subregisters when the register coalescer eliminates identity copies. The fundamental problem is complexity from the fact that undef values are a special case since they don't have an associated VNInfo/Segment unless the value is used across blocks. For example, in this case, %0 has 2 subregisters sub0 and sub1:

> Only if the recursion is very deep. In practice, a recursive descent > parser isn't going to run out of stack space, nor will a quicksort or > binary-tree walker, The recursive-descent parser case has happened in practice: http://my.opera.com/hallvors/blog/2012/07/17/twitter-crashes-itself-with-commas?1 Also, I've seen some recursion-related PR's in Clang, although I think

Are there any plans to support generation of DWARF DIEs needed for languages other than C, C++, and Obj-C? For example, ADA would need more capability and so would several other "experimental" new languages that use LLVM. Just as one simple example, the "subrange" type can be used with variables in many languages. Right now, LLVM only supports "subrange" in the

On Wed, 4 Jul 2007, David A. Greene wrote: > On Monday 02 July 2007 23:24, David A. Greene wrote: >>>> - Changing the API >>>> a) Template it to take two iterators. This causes code size bloat. >> >> This seems like the right solution to me. Unless llvm is running on >> extremely limited memory embedded systems, the extra code space >>

I've been working on patches to improve subregister liveness tracking on llvm and I wanted to inform the llvm community about the overal design/motivation for them. I will send the patches to llvm-commits later today. Greetings Matthias Braun Subregisters in llvm ==================== Some targets can access registers in different ways resulting in wider or narrower accesses. For

Hello, I have a minimal testcase which crashes RegisterCoalescer in my out-of-tree target. It only crashes in Debug builds of llc---not in Release builds. Also, interesting to note that the x86 backend lowers this same testcase successfully. I did a quick search of bugs.llvm.org and found no matches. This implies that the problem is in my backend and/or how my backend interacts with

On Wed, Oct 3, 2012 at 10:15 AM, Matthieu Moy <Matthieu.Moy at grenoble-inp.fr> wrote: > Preston Briggs <preston.briggs at gmail.com> writes: >> Think about costs asymptotically; that's what matters. Calls and >> returns require constant time, just like addition and multiplication. > > Constant time, but not necessarily constant memory. > > Deep recursion

Currently it will always spill / restore the whole vreg but only spilling the parts that are actually live would be a nice addition in the future. Looking at r192119': if "mtlo" writes to $LO and sets $HI to an unpredictable value, then it should just have an additional (dead) def operand for $hi, shouldn't it? Greetings Matthias Am 10/8/13, 11:03 AM, schrieb Akira

...ometime last spring, with the discovery that the > debug info passed through LLVM is in fact, equivalent to only a small subset of > Dwarf. The decisive discovery was that the debug info for a subrange type does not > allow a base type to be noted, even though Dwarf does. Modula-3 allows subranges > of any of a few builtin types and an extremely large potential set of programmer-defined > enumeration types, so this is pretty much unusable for subranges. We are certainly interested in supporting more DWARF features in LLVM's DWARF backend and metadata. While the amount of code nece...

On Monday 02 July 2007 23:24, David A. Greene wrote: > > > - Changing the API > > > a) Template it to take two iterators. This causes code size bloat. > > This seems like the right solution to me. Unless llvm is running on > extremely limited memory embedded systems, the extra code space > shouldn't be an issue. It turns out this wasn't quite a simple as

What I didn't mention in r192119 is that mthi/lo clobbers the other sub-register only if the contents of hi and lo are produced by mult or other arithmetic instructions (div, madd, etc.) It doesn't have this side-effect if it is produced by another mthi/lo. So I don't think making mthi/lo clobber the other half would work. For example, this is an illegal sequence of instructions,

Hello I'm reading http://llvm.org/docs/SourceLevelDebugging.html and some things aren't clear. There are a couple of references made to %llvm.dbg.variable, which isn't defined anywhere. It it an intrinsic? A global? Could it be a relic from the old debug info docs (where it *is* defined?). The same goes for llvm.dbg.derivedtype and llvm.dbg.subrange which are also referenced but not

On Tuesday, 5 November 2019 01:37:15 PST Rowland penny via samba wrote: > On 04/11/2019 18:52, Alexey A Nikitin wrote: > > On Sunday, 3 November 2019 01:41:18 PST Rowland penny via samba wrote: > >> As I said, you cannot use 'winbind use default domain = yes' with > >> 'autorid', it makes all users and groups members of the same domain, > >> this

On Sunday, 3 November 2019 01:41:18 PST Rowland penny via samba wrote: > As I said, you cannot use 'winbind use default domain = yes' with > 'autorid', it makes all users and groups members of the same domain, > this is probably what has happened here. > > Remove the line, this should stop it happening again > > If you have only one domain, then you

On Oct 8, 2013, at 2:06 PM, Akira Hatanaka <ahatanak at gmail.com> wrote: > What I didn't mention in r192119 is that mthi/lo clobbers the other sub-register only if the contents of hi and lo are produced by mult or other arithmetic instructions (div, madd, etc.) It doesn't have this side-effect if it is produced by another mthi/lo. So I don't think making mthi/lo clobber the

It''s safe and easy to do so, provided the ranges don''t overlap. Signed-off-by: Li Zefan <lizf@cn.fujitsu.com> --- fs/btrfs/ioctl.c | 23 ++++++++++++++++------- 1 files changed, 16 insertions(+), 7 deletions(-) diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c index 0b06a5c..8fcd671 100644 --- a/fs/btrfs/ioctl.c +++ b/fs/btrfs/ioctl.c @@ -2223,8 +2223,6 @@ static

I am, as this question will make very obvious, not exactly a guru when it comes to audio under Linux. I'd like to record some prompts using a nice microphone and my Ensoniq sound card, and then convert them to gsm/wav for use with asterisk. What Linux command would I use to a) do the recordings, and then b) convert them to the appropriate formats? I know there are