search for: stmts

Displaying 20 results from an estimated 24 matches for "stmts".

Did you mean: stats
2013 May 06
2
[LLVMdev] convert switch stmts to If statements
Hi All, Is there a pass in llvm that converts switch statements to if statements? George -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130506/f06741c4/attachment.html>
2013 May 06
0
[LLVMdev] convert switch stmts to If statements
----- Original Message ----- > From: "George Baah" <georgebaah at gmail.com> > To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Monday, May 6, 2013 3:09:33 PM > Subject: [LLVMdev] convert switch stmts to If statements > > > > > Hi All, Is there a pass in llvm that converts switch statements to if > statements? > What do you mean by convert? SelectionDAGBuilder::visitSwitch in lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp converts the switch statements for code gener...
2013 May 06
2
[LLVMdev] convert switch stmts to If statements
....gov> wrote: > ----- Original Message ----- > > From: "George Baah" <georgebaah at gmail.com> > > To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > > Sent: Monday, May 6, 2013 3:09:33 PM > > Subject: [LLVMdev] convert switch stmts to If statements > > > > > > > > > > Hi All, Is there a pass in llvm that converts switch statements to if > > statements? > > > > What do you mean by convert? SelectionDAGBuilder::visitSwitch in > lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp c...
2013 May 06
0
[LLVMdev] convert switch stmts to If statements
...l.gov> wrote: > ----- Original Message ----- > > From: "George Baah" <georgebaah at gmail.com> > > To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > > Sent: Monday, May 6, 2013 3:09:33 PM > > Subject: [LLVMdev] convert switch stmts to If statements > > > > > > > > > > Hi All, Is there a pass in llvm that converts switch statements to if > > statements? > > > > What do you mean by convert? SelectionDAGBuilder::visitSwitch in lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp conve...
2012 Sep 11
4
[PATCH] libxl: Tolerate xl config files missing trailing newline
...t;atom", "valuelist", "values", "nlok", 0 + "''=''", "'';''", "''[''", "'']''", "'',''", "$accept", "file", "stmts", "stmt", + "assignment", "endstmt", "value", "atom", "valuelist", "values", "nlok", 0 }; #endif @@ -477,15 +479,17 @@ static const yytype_uint16 yytoknum[] = /* YYR1[YYN] -- Symbol number of symbol that rule...
2010 Mar 31
2
[LLVMdev] CFG entry and exit blocks
...pass's getReturnBlock function returns null (see UnifyFunctionExitNodes.h), I'm back to square one of not having a single exit block. I'm wondering what would cause a CFG not to have a return block. The comments in UnifyFunctionExitNodes.cpp say: "If there are no return stmts in the Function, a null pointer is returned." But this doesn't make sense; even an empty void function has a return block with a ret instruction inside it. Is there some other kind of source code pattern that would cause an absence of a return block? Thanks, Trevor
2018 Aug 29
4
Identifying objects within BumpPtrAllocator.
In various debug dumps (eg., Clang's -ast-dump), various objects (eg., Stmts and Decls in that -ast-dump) are identified by pointers. It's very reliable in the sense that no two objects would ever have the same pointer at the same time, but it's unpleasant that pointers change across runs. Having deterministic identifiers instead of pointers would aid debugging:...
2010 Mar 31
0
[LLVMdev] CFG entry and exit blocks
On Wed, Mar 31, 2010 at 2:59 PM, Trevor Harmon <trevor.w.harmon at nasa.gov> wrote: > I'm wondering what would cause a CFG not to have a return block. The > comments in UnifyFunctionExitNodes.cpp say: "If there are no return > stmts in the Function, a null pointer is returned." But this doesn't > make sense; even an empty void function has a return block with a ret > instruction inside it. Is there some other kind of source code pattern > that would cause an absence of a return block? Yes, an infinite loop....
2018 Aug 29
3
[cfe-dev] Identifying objects within BumpPtrAllocator.
...r dumping facilities could greatly benefit as well. > >> On Aug 28, 2018, at 5:14 PM, Artem Dergachev via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote: >> >> In various debug dumps (eg., Clang's -ast-dump), various objects (eg., Stmts and Decls in that -ast-dump) are identified by pointers. It's very reliable in the sense that no two objects would ever have the same pointer at the same time, but it's unpleasant that pointers change across runs. Having deterministic identifiers instead of pointers would aid debugging: ima...
2003 May 31
5
CAC ADIT600 / T400 config
I know a few ppl have those CAC Adit 600's with t400 I can't seem to get my second span up on the T400 connected to the second spand on the adit (A:2) A:1 seems ok Can someone post they zaptel.conf span defintions And maybe a "print config" from the adit 600 cli I think my issue is timing srcs the coding, framing. bld out are all matched thx -------------- next part
2010 Mar 31
0
[LLVMdev] CFG entry and exit blocks
Dear Trevor, I'm too lazy to convert your .dot file into a graph file, but I'll make some comments anyway. :) First, LLVM does not guarantee that a function has a single exit block. Multiple basic blocks can have a return instruction as their terminator instruction. There is a pass (Unify Function Exit nodes i.e., -mergereturn <http://llvm.org/docs/Passes.html#mergereturn>)
2015 Aug 19
3
RFC: PGO Late instrumentation for LLVM
...re-inline 199.924 248.7% 70762720 (5) (4) + Silva 119.904 149.2% 24499528 Config(5) used the simple heuristic that Sean Silva proposed: not instrumenting single BB functions that contain less than 10 instructions (excluding debug and phi stmts). We can see: 1) Simple heuristic of not instrumenting small single BB functions improves instrumentation performance as expected. 2) Using simple heuristic is still slower than late instrumentation with pre-inlining: the later is 15% faster. 3) Late instrumentation produces the smallest profile s...
2010 Mar 31
2
[LLVMdev] CFG entry and exit blocks
Hi, I'm confused about the entry and exit blocks of an LLVM CFG. I understand that every CFG has one and only one entry block, and this is confirmed by the existence of the getEntryBlock function in the Function class. But what about exit (a.k.a. return) blocks? At first I assumed that LLVM CFGs have one and only one exit block, too, but the following code is a counter-example:
2014 Jun 12
2
[PATCH] fuse: UID 0 should override all permissions checks (RHBZ#1106548).
Previously if you were root, and you tried to change directory into a directory which was not owned by you and not readable (eg. 0700 bin:bin), it would fail. This doesn't fail on regular directories because when you are root the kernel just ignores permissions. Although libguestfs in general tries not to duplicate kernel code, in the case where we emulate the FUSE access(2) system call,
2012 Dec 27
2
A Couple Questions About a New Project
My compliments on the release of syslinux-5.0 and happy holidays to the entire Syslinux team.? I have a longer message in me.? Lots of curiousity about the direction of the project, but that will have to wait until I finish my first 5.0 project (*not* my first Syslinux project), which just happens to touch past problems: drive enumeration. This particular effort is on a USB flash drive, with two
2015 Sep 01
3
RFC: PGO Late instrumentation for LLVM
...248.7% 70762720 > (5) (4) + Silva 119.904 149.2% 24499528 > > Config(5) used the simple heuristic that Sean Silva proposed: not > instrumenting single BB functions that contain less than 10 instructions > (excluding debug and phi stmts). > > We can see: > 1) Simple heuristic of not instrumenting small single BB functions > improves instrumentation performance as expected. > 2) Using simple heuristic is still slower than late instrumentation with > pre-inlining: the later is 15% faster. > 3) Late instrumentati...
2016 Oct 20
2
[Bug 1092] New: nft v0.6 segfault in must_print_eq_op at expression.c:520 during 'nft monitor trace' in netdev filter
...db) bt full #0 0x00000047a69fce5a in must_print_eq_op (expr=0x47a8a13610, expr=0x47a8a13610) at expression.c:520 No locals. #1 binop_expr_print (expr=0x47a8a13610) at expression.c:532 No locals. #2 0x00000047a6a05888 in trace_print_packet (nlt=nlt at entry=0x47a8a22050) at netlink.c:2380 stmts = {next = 0x47a8a0cc90, prev = 0x47a8a12a90} pctx = {pbase = PROTO_BASE_INVALID, pdep = 0x0, prev = 0x0} ctx = {family = 5, protocol = {{location = {indesc = 0x0, {{token_offset = 0, line_offset = 0, first_line = 0, last_line = 0, first_column = 0, last_column = 0}, {nle = 0x0}}}, d...
2014 Aug 20
4
[LLVMdev] Proposal for ""llvm.mem.vectorize.safelen"
----- Original Message ----- > From: "Arnold Schwaighofer" <aschwaighofer at apple.com> > To: "Johannes Doerfert" <doerfert at cs.uni-saarland.de> > Cc: llvmdev at cs.uiuc.edu, "Arch Robison" <arch.robison at intel.com> > Sent: Wednesday, August 20, 2014 11:29:16 AM > Subject: Re: [LLVMdev] Proposal for
2015 Sep 17
0
[ANNOUNCE] nftables 0.5 release
...lper function netlink_linearize: add register dumping helper function parser: properly fix handling of large integer values set: remove unused set_clone() function expr: fix crash when listing non-verdict mappings meta: don't print meta keyword for unqualified meta stmts evaluate: verify named map is actually a map evaluate: properly set datatype of map expression evaluate: check that map expressions' datatype matches mappings evaluate: use stmt_evaluate_arg() in all cases set_elem: convert flag value to inclusive-OR binops during...
2003 Nov 24
11
Picking an open channel (FXO port) for outbound calls
Greetings: I did some quick searching of my history of this list, and I tried a quick Google search as well, but perhaps someone on the list can quickly answer this question. I have a very nicely working Asterisk system at home with two Digium X100P FXO cards. When my SIP phones want to dial-out I have them setup to grab the first analog card (Zap/1) with the following extensions.conf segment: