search for: trivial

...s going from 1.4.4 to 1.4.6 so lets try the trunk via SVN [CXX] chan_vpb.cc -> chan_vpb.oo chan_vpb.cc:3055:9: error: macro "AST_MODULE_INFO" passed 7 arguments, but takes just 6 chan_vpb.cc:379: error: invalid conversion from \xe2 to \xe2 chan_vpb.cc:379: sorry, unimplemented: non-trivial designated initializers not supported chan_vpb.cc:379: sorry, unimplemented: non-trivial designated initializers not supported chan_vpb.cc:379: sorry, unimplemented: non-trivial designated initializers not supported chan_vpb.cc:379: sorry, unimplemented: non-trivial designated initializers not supp...

...%cond1, label %continue, label %loop_exit continue: %var_val = load i32, i32* %var br i1 %cond2, label %do_something, label %loop_exit do_something: call void @some_func() noreturn nounwind br label %loop_begin loop_exit: ret i32 0 } Assume you don't have enough budget to do non-trivial loop unswtich (for test purpose, set -loop-unswitch-threshold=0 with opt), the result would be: define i32 @test(i32* %var, i1 %cond1, i1 %cond2) { br i1 %cond1, label %..split_crit_edge, label %.loop_exit.split_crit_edge .loop_exit.split_crit_edge: ; preds = %0 br label...

How does LLVM define "indirect call"? The documentation of CallSiteBase::getCalledFunction claims it returns null for indirect calls, but in practice it seems to return null for "non-trivial" calls. For example, it returns null for a direct call to a bitcast'ed function: %0 = call void bitcast (void (%struct.foo *)* @func to void (%struct.bar *)*)(%struct.bar *qux) By some definition "direct" could mean "trivial", but here it seems ambiguous at best....

Is there any written description of what "non trivialness" is there? On Sun, Apr 29, 2018, 2:49 PM Chandler Carruth via llvm-dev < llvm-dev at lists.llvm.org> wrote: > One of the last big missing pieces for the new PM is enabling non-trivial > loop unswitch at O3. > > The pass is now working well and passing all the testing I...

I'm running into a problem with subregs during trivial coalescing in the linear scan allocator. Should RALinScan::attemptTrivialCoalescing be allowed to coalesce a COPY that uses a subreg as a destination? I've got the following sequence of code (unfortunately for an out of tree target) that is moving 32 and 64 bit sub-registers around within a 1...

One of the last big missing pieces for the new PM is enabling non-trivial loop unswitch at O3. The pass is now working well and passing all the testing I have done as well as some others' testing (thanks Fedor!) so it should be ready to be enabled. I've done preliminary benchmarking on the test suite and SPEC and haven't seen any interesting regressions and...

I have encountered a rather odd situation with Greedy where it will end up spilling a register that was populated with a zero (with a trivially rematerializable load-immediate instruction). In fact, it spills 3 such values (LICM moves stuff out of a loop, register coalescer replaces copies with load-immediates and then Greedy spills them). I personally can't think of a situation where a spill (with a reload later presumably) is bett...

I wanted to make sure that everyone was aware of a slight change we''ve made to the process for open source contributions. For *trivial* contributions, we are no longer requiring a Contributor License Agreement (CLA). Note that for most contributions a CLA signature is still required. I''m also working on making the overall CLA process easier, but that will take a little more time to overhaul. You can see more about our de...

...niil Troshkov <troshkovdanil at gmail.com> wrote: > > Hi! > > I have not found test case. (It is because we have no target using "ExpandInsertToVectorThroughStack"). > But I tested it for target currently not included in llvm trunk. > > This fix correct and trivial, so I'm offering to commit it... > > On Wed, Nov 12, 2014 at 11:47 PM, Daniil Troshkov <troshkovdanil at gmail.com <mailto:troshkovdanil at gmail.com>> wrote: > I detected this bug using test case from platform which is not currently supported on llvm targets. (Our team is...

...tcase? > > —Owen > > > On Nov 12, 2014, at 5:52 AM, Daniil Troshkov <troshkovdanil at gmail.com> > wrote: > > > > Hi Owen! > > > > The "First store the whole vector" is without uses and will be deleted > later. > > I've attached trivial patch to fix it. > > I have no commit access so if patch is OK, please, commit it . > > > > Danil. > > <ExpandInsertToVectorThroughStack.patch> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail...

On Mon, Oct 7, 2019 at 7:39 AM Jani Nikula <jani.nikula at linux.intel.com> wrote: > > On Fri, 04 Oct 2019, Krzysztof Kozlowski <krzk at kernel.org> wrote: > > drivers/gpu/drm/i915/Kconfig | 12 +- > > drivers/gpu/drm/i915/Kconfig.debug | 144 +++++++++++------------ > > Please split these out to a separate patch. Can't speak for others,

Hi, This is a very trivial question, and I do not know why I cannot remember the answer at all! How does one get the entire system information (which OS, R version....etc) using an R command? Thanks, Kevin ------------------------------------------------------------------------------ Ko-Kang Kevin Wang Postgraduate PGDi...

...by service auth { user } Usage: /etc/init.d/dovecot {start|stop|reload|restart|force-reload} tail /var/log/maillog Oct 20 10:13:59 example postfix/smtpd[28141]: warning: problem talking to service rewrite: Success Oct 20 10:13:59 example postfix/master[4000]: warning: process /usr/libexec/postfix/trivial-rewrite pid 30178 exit status 1 Oct 20 10:13:59 example postfix/master[4000]: warning: process /usr/libexec/postfix/trivial-rewrite pid 30179 exit status 1 Oct 20 10:13:59 example postfix/smtpd[28458]: warning: problem talking to service rewrite: Success Oct 20 10:13:59 example postfix/master[4000]...

Hi, I’m looking at some patterns which failed to import, and when I reduced them I was surprised to find a variety of complicated patterns successfully import, but the most trivial patterns I can come up with fail. If I add this pattern to test/TableGen/GlobalISelEmitter.td: def : Pat < (mul i32:$y, i32:$x), (MUL $x, $y) >; test/TableGen/GlobalISelEmitter.td:1196:1: warning: Skipped pattern: Dst pattern child is an unsupported kind def : Pat < What am I missin...

...of the size field, VMKit emits a GetArrayLength > call, flagged readnone. The GVN pass will merge all GetArrayLength of a > same array and the LICM pass will hoist the call. Once theses passes are > complete, VMKit lowers the call to > the actual load. Right, so that part should be trivial. So, does the array bounds check elimination already work? If it does, that will considerably reduce the work that Andre needs to do. To say the least... Andrew.

Hi Owen! The "First store the whole vector" is without uses and will be deleted later. I've attached trivial patch to fix it. I have no commit access so if patch is OK, please, commit it . Danil. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141112/52592eeb/attachment.html> -------------- next part -----------...

...> the patch looks like it'll be conflicts galore and a problem to manage >> > if merged in one big lump. >> >> Yes, it would be nice to have the amd patch separate as well. > > I'll split the AMD and i915 although I am not sure if it is sense to > split such trivial patch per each driver. Thanks. See MAINTAINERS, many of the drivers are maintained in the same drm-misc repo, and it makes no difference to split those. In general it's, well, trivial to split up patches like this per driver or repo, but not splitting it up generates extra busywork in managi...

That's an unintentional change. However, the reason for this change was to make optional of trivially copyable types trivially copyable, adding a user-provided move ctor would break that again :( I'm leaning towards making the non-trivial version of llvm::Optional more like std::optional. In the long term std::optional is going to replace llvm::Optional. How bad would that be for your use ca...

...21, Friedman, Eli wrote: > On 9/12/2018 11:51 AM, via llvm-dev wrote: >> How does LLVM define "indirect call"? The documentation of >> CallSiteBase::getCalledFunction claims it returns null for indirect >> calls, but in practice it seems to return null for "non-trivial" >> calls. For example, it returns null for a direct call to a bitcast'ed >> function: >> >> %0 = call void bitcast (void (%struct.foo *)* @func to void >> (%struct.bar *)*)(%struct.bar *qux) >> >> By some definition "direct" could m...

On Wed, Jan 24, 2018 at 11:47 PM, Benjamin Kramer <benny.kra at gmail.com> wrote: > That's an unintentional change. However, the reason for this change > was to make optional of trivially copyable types trivially copyable, > adding a user-provided move ctor would break that again :( > > I'm leaning towards making the non-trivial version of llvm::Optional > more like std::optional. In the long term std::optional is going to > replace llvm::Optional. How bad would...