similar to: Error-Running pass 'Function Pass Manager' on module

Hi Zide, I think I found the right way to reach my goal. I used the following command: clang -O3 -Xclang -disable-llvm-optzns main.c -S -emit-llvm -o main.ll to generate an IR file enriched by all the metadata that otherwise wouldn't be generated with -O0. Moreover, -disable-llvm-optzns flag ensures that none of the optimization passes has been applied yet to the IR. In this way, I can

Hi, Stefano I also have the problem as described by Emanuele. You say that clang schedules target-independent and target-dependent passes. However, when I use lli to execute bitcode generated by opt with -O3 or with the same optimization passes as -O3, the performance are still different. So, are there some special operations by -O3 option? I read the source code of opt, but I cannot find the

Hi everyone, I want to test the passes in llvm, and I got some passes sequences that caused the crash of opt. Although I can use bugpoint to narrow down the source of problems, I can only get some reduced and simplified IR and passes to reproduce the problem. My question is how to get the reduced IR of the original IR file to reproduce the problem. For example, "opt a.bc -a -b -c -d (where

Hi there, I am working with opt-6.0 and try to generate a call graph of libsndfile, but it seems the call graph doesn't cover all call relationship. Actually, I am doing static analysis on *CVE-2014-8130*, which is a zero division on libtiff/tif_write.c TIFFWriteScanline. (see https://security-tracker.debian.org/tracker/CVE-2014-8130) Theoretically, the main function in

Hi, developers, Recently, I read two papers [1], [2] about finding the root causes of compiler bugs. However, I do not find any information in these paper about how compiler developers find the root causes of compiler bugs in practice. So I am curious whether these techniques are useful in practice. For my experience, the outputs of compilers are always used to isolate the causes of compiler

Hello, first of all: I'm new to R and have only used SPSS befor this (which can't do this at all...). I'm trying to output some regression results to latex. The regressions are normal OLS and I'm trying to output the results with standardized regression coefficients and t-statistics based on "Huber-White sandwich estimator for variance". The final result should be

Hi all, I would like to be sure that Tablegen still does not support completely separate multiple instruction generation, and the only way is to write costume code (may be in TargetISelDAGToDAG class) to get the needed result. Dear Tom, do you found other solution (using Tablegen tool) for this? Thanks, Arsen -- View this message in context:

Dear Tom, What is the advantage to use the “pseudo instruction” approach VS “custom lowering/DAGtoDAGSelection” VS “ Library function”? Best Kevin On Aug 14, 2014, at 9:27 AM, Tom Stellard <tom at stellard.net> wrote: > On Thu, Aug 14, 2014 at 12:05:33AM -0700, Arsen Hakobyan wrote: >> Hi all, >> >> I would like to be sure that Tablegen still does not support

Hai, I know, im not the best in english, but i've updated the time sync page on the wiki. If someone can check it and update where needed. I've added this part. https://wiki.samba.org/index.php/Time_Synchronisation#Requirements_2 And https://wiki.samba.org/index.php/Time_Synchronisation#Set_up_time_with_systemd-timesyncd_on_a_Unix_Domain_Member Greetz, Louis

Great! Thanks everyone for the input, I'm going to start splitting up the patch. I'll send out the non-mechanical parts separately. On Wed, Oct 31, 2018 at 10:03 PM Chris Lattner <sabre at nondot.org> wrote: > On Oct 31, 2018, at 2:24 PM, Reid Kleckner <rnk at google.com> wrote: > > Alex Kornienko proposed enabling this warning back in 2012 here: >

Hi, The subject says it all. Is it possible to put the IP address of the peer in the CDR records? Using AGI maybe? -- Kind regards, Signet bv Remco Bressers T 040 - 707 4 907 F 040 - 707 4 909 E rbressers at signet.nl

Hi, I'm trying to create a Pattern that looks something like this: def my_inst : Instruction < let OutOperandList = (outs REG:$dst); let InOperandList = (ins imm:$src); let Uses = [R0]; > def int_my_intrinsic : Intrinsic < [llvm_float_ty], [llvm_i32_ty, llvm_i32_ty, llvm_i32_ty], [] >; def : Pattern < (int_my_intrinsic imm:$a, imm:$b, imm:$c), [(set R0, (MOV_IMM

On Thu, 11 Oct 2018 at 00:28, Thomas Lively via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I just wanted to bump this to see if anyone has any input. I would really like to get these landed soon if there are no objections. Hi Thomas, With ISD::FMINNAN and ISD::FMAXNAN now easy to produce for any target due to these newly exposed intrinsics, I think these nodes should be handled

I just want to point out that the issue of incompatible history is not new. This has been getting discussed all the way back in July 2016. http://lists.llvm.org/pipermail/llvm-dev/2016-July/102657.html <http://lists.llvm.org/pipermail/llvm-dev/2016-July/102657.html> As James said in that email: > That we'll be getting incompatible history has been glossed over, and it is >

Hello A 4.4% geomean codesize improvement is really impressive. That stuff is hard to come by, you usually have to nibble away at it bit at a time. I ran some codesize benchmarks we have and they were in the same ballpark. Some of these are quite small so had less opportunity for outlining, but the average was still over 3% with some as high as 9-10%. All the tests I ran were fine, although we

jduran wrote: > Your wisdom please! Sennheiser is a reputable brand. The model you cited is in their lowest cost series. I have sold a number of these systems over the years. Their first generation (not G2) were problematic in not being very durable. I don't have as much experience with the G2, but the few we have sold have worked fine for several years. My first choice for most

*From:* flang-dev <flang-dev-bounces at lists.flang-compiler.org> *On Behalf Of *Eric Schweitz (PGI) *Sent:* Thursday, November 01, 2018 1:02 PM *To:* flang-dev at lists.flang-compiler.org *Subject:* [Flang-dev] RFC: Adding debug information to LLVM to support Fortran In order to support debugging in the Flang project, work has been done to extend LLVM debug information for the Fortran

Regarding flags, I was just thinking that maybe we should invent a new DISubprogramFlags type. DISubprogram already has a few bitfields for subprogram-specific things, Fortran will want 3 more, and there's no reason to fill up the generic DIFlags with more bits that are used in only one class. I agree that the array stuff needs to be designed with an eye to handling how other languages do

https://bugs.freedesktop.org/show_bug.cgi?id=108500 Bug ID: 108500 Summary: Crash when creating a depth buffer on GeForce 320M Product: Mesa Version: 18.2 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: Drivers/DRI/nouveau

On Thu, Nov 1, 2018 at 1:22 AM Vedant Kumar via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > Hi all, > >> On Oct 31, 2018, at 11:18 AM, Nico Weber via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi, >> >> first things first: If you're happy with cmake, you can stop reading now. >> I'm not, I just put up with it :) > ...