search for: directives

libswfdec/swfdec_as_math.c | 10 +++++++++- test/trace/Makefile.am | 9 +++++++++ test/trace/round-direction-5.swf |binary test/trace/round-direction-5.swf.trace | 5 +++++ test/trace/round-direction-6.swf |binary test/trace/round-direction-6.swf.trace | 5 +++++ test/trace/round-direction-7.swf |binary

...eeded a clear, intuitive conceptual model. And then someone to make it work that way (hi Joel!). Basic Conceptual Model ---------------------- FileCheck should operate on the basis of these three fundamental concepts. (1) Search range. This is some substring of the input text where one or more directives will do their pattern-matching magic. (2) Match range. This is a substring of a search range where a directive (or in one case, a group of directives) has matched a pattern. (3) Directive groups. These are sequences of adjacent directives that operate in a related way on a search range. Direct...

...then someone to make it work that way (hi > Joel!). > > Basic Conceptual Model > ---------------------- > > FileCheck should operate on the basis of these three fundamental > concepts. > > (1) Search range. This is some substring of the input text where one > or more directives will do their pattern-matching magic. > > (2) Match range. This is a substring of a search range where a > directive (or in one case, a group of directives) has matched a > pattern. > > (3) Directive groups. These are sequences of adjacent directives that > operate in a relat...

* compiled from cvs, i am trying call ip phones in callmanager 3.2 10.17.0.2 is my callmanager i noticed from network dumps that instead of sending rtp to the ip phone, * sends it to 10.17.0.2! thereby causing no audio from * to ip phone. audio from ip phone to * is ok. only callmanager calls fail. netmeeting works ok... here is the debug, thanks for any info ~kelvin H323 debug enabled --

...) to load_linux.c:bios_boot_linux() because > >> > there is no convenient way in new_linux_kernel() to control the boot > >> > flags value. > >> > >> This is the part that has me questioning things and trying to recall > >> if any other KERNEL-like directives ever utilize keeppxe. > >> > > > > @Gene, > > > > Not being a developer myself, I don't understand this "other > > KERNEL-like directives" sentence. I do know what "kernel-like > > Those directives which acts like KERNEL, specifying a...

...t [constrain DAG to a single line] for the sake of matching unordered text on a single line. SAME after DAGs is as close as I can get to that. Maybe we need a CHECK-DAG-SAME. Hmmm. You know, there were cases where people wrote tests that tried to use combo suffixes like that, but of course those directives were not actually executed (because they were treated like a SAME with prefix CHECK-DAG (or whatever), rather than CHECK with two suffixes). That's why some while ago I added checks within FileCheck to try to detect duplicate suffixes and complain. There were, I don’t remember, a couple dozen...

# I am sure that I could be more efficient than this but how? Thanks in advance. #GPS in Decimal Degrees in the form longitude latitude RM215 <- matrix(c(-82.1461363, 33.5959109), nrow=1) SC <- matrix(c(-82.025888, 33.606454), nrow=1) RM202 <- matrix(c(-81.9906723, 33.5027653), nrow=1) RM198 <- matrix(c(-81.926823, 33.4634678), nrow=1) HC <- matrix(c(-81.920505, 33.46192), nrow=1)

Andrew Lenharth wrote: > If I remember correctly, it only tries to resolve indirect calls. The > analysis doesn't track direct calls because you can do it just as well > yourself. DSCallGraph::callee_begin() and DSCallGraph::callee_end() cooperate to iterate over an empty set (EmptyActual) for any call site not found in the ActualCallees map. So if direct calls are not tracked,

> On Thu, Apr 21, 2016 at 10:30 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > > Would someone please be so kind to explain / describe the PXERETRY > > directive? > > $ git grep -ni pxeretry > com32/elflink/ldlinux/readconfig.c:1305: else if (looking_at(p, "pxeretry")) > com32/elflink/ldlinux/readconfig.c:1306: PXERetry = >

Ady asked: > Have you read the "See also" section(s) of the wiki page(s)? Yes. > By reading the relevant wiki pages, a user should (_hopefully_) get to > the conclusion that the PATH directive is relevant for c32 modules, and > not a replacement for the CONFIG / INCLUDE directives nor for relative > paths based on the "Working Directory". There's nothing in Directives/path that says it applies only to c32. Rephrasing the first sentence on that page: When attempting to open a file name, the CWD is searched first, before PATH. Perhaps that should be:...

> > kernel.c:new_linux_kernel() to load_linux.c:bios_boot_linux() because > > there is no convenient way in new_linux_kernel() to control the boot > > flags value. > > This is the part that has me questioning things and trying to recall > if any other KERNEL-like directives ever utilize keeppxe. > @Gene, Not being a developer myself, I don't understand this "other KERNEL-like directives" sentence. I do know what "kernel-like directives" means, but I do not know which one is the one you are referring to here, and why "_other_ KERNE...

Hi, :If I compile this file with debugging enabled (clang/LLVM TOT) int main() { } I get the error Error: inconsistent uses of .cfi_sections From the 2.27 binutils assemblers. It seems that 2.27 doesn't like the .cfi_sections .debug_frame directive following previous .cfi directives. The assemblers seem to be happy if the .cfi_sections directive precedes any other .cfi directive. Is this a bug in binutils or LLVM? It looks as if a fix might be to move the generation of the .cfi_sections directive from endModule() to somewhere else (maybe a non-existant beginModule()?). Co...

Currently diagnostics related to objc_direct/objc_non_runtime_protocol are done at each compilation unit. Even with these diagnostics, we will see issues at runtime - Due to lack of global scope for our diagnostics. We can catch these issues with a global analysis. - Due to usages of dynamic APIs that require the metadata. We can catch these issues with runtime checks. Builds with

Hello all, I was reading up on SMB Direct support and it seems very interesting. I looked through slides of a presentation by Stefan Metzmacher about SMB Direct last year: https://www.samba.org/~metze/presentations/2018/SDC/StefanMetzmacher_SDC2018-SMB-Direct-Status-rev1-presentation.pdf I was wondering what the current support of of SMB Direct for Samba. I have a Windows 10 Pro for Workstations

I use POSIXct for datetimes. Is thee a timeAlign function that I can use where : align by year direction -1 ==> start of this year direction 1 ==> start of next year align by week direction -1 ==> date on last sunday direction 1 ==> date on next sunday align by day direction -1 ==> time at past midnight direction 1 ==> time at this comming

I have a question about the PATH directive. In fact, the question is not about how it is currently working, but about its intention or goal, or how it was supposed to work (or how it was thought about for the 5.00 release). Previous discussions about the PATH directive in the Syslinux Mailing List, and its documentation (e.g. "PATH rules") left on me the impression that it was

On Tue, Aug 9, 2011 at 10:45 PM, Ben Liblit <liblit at cs.wisc.edu> wrote: > Andrew Lenharth wrote: >> If I remember correctly, it only tries to resolve indirect calls.  The >> analysis doesn't track direct calls because you can do it just as well >> yourself. > > DSCallGraph::callee_begin() and DSCallGraph::callee_end() cooperate to > iterate over an empty

The attached patch makes the AsmPrinter emit one .weak directive for each weak global variable that is referenced at least once in a global table. It uses a std::set to print only one directive. Thoughts? Best Regards, Rafael -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm.patch Type: text/x-patch Size: 2945 bytes Desc: not available URL:

I am trying to calculate coordinate transformations and in the process of debugging my code using debug I found the following Browse[1]> direction[i] [1] -1.570796 Browse[1]> cos(direction[i]) [1] 6.123032e-17 Browse[1]> cos(-1.570796) [1] 3.267949e-07 Browse[1]> direction[i] [1] -1.570796 Browse[1]> cos(direction[i]) [1] 6.123032e-17 Browse[1]> cos(-1.570796) [1] 3.267949e-07

2018-01-16 18:18 GMT+08:00 Tim Northover <t.p.northover at gmail.com>: > On 15 January 2018 at 12:49, 陳韋任 via llvm-dev <llvm-dev at lists.llvm.org> > wrote: > > - CFI directives: > > > > This is for .eh_frame section. Basically all the targets insert CFI > > directives in FrameLowering, but I am not sure exactly when/where I > should > > do so. > > The directives are there to describe where the unwinder should look to > find out what...