search for: 20200711

Displaying 15 results from an estimated 15 matches for "20200711".

2020 Jul 11
3
is a MachineBasicBlock a kind of superblock?
...look like. Any suggestions for that will be appreciated. thanks, Chris BTW, this is at the MI-MC interface. The IR BasicBlock is a completely different issue. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200711/44c1b258/attachment.html>
2020 Jul 11
1
16.11.1 release removed from current
...robably better practice to pull source tarballs from old-releases, but is there a reason that the current "released" version was pulled? Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20200711/eaa3895c/attachment.html>
2020 Jul 11
0
OBi202 and auto answer
...r is it named something else ? I'd like an incoming call to set two things: 1) No ring 2) Auto answer Anyone found a way to do those ? Thanks Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20200711/aa5c5928/attachment.html>
2020 Jul 11
3
Bug in pass 'ipsccp' on function attribute 'argmemonly'?
Hi all, Let's see an example (from Alexandre Isoard) first: **************************************************************************************** ; RUN: opt -ipsccp -deadargelim -licm -O2 -S < %s @g = internal global i32 0 ; Function Attrs: argmemonly define internal void @foo(i32* nonnull dereferenceable(4) %arg, i32 %val) #0 { entry: store i32 %val, i32* %arg ret void } define
2020 Jul 10
2
Installing ice cast with SSL support
...--prefix=/usr/serverok/icecast --with-curl --with-openssl If the first option is indeed possible I would prefer that. Can anyone confirm it is possible? Damian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200711/b199ce98/attachment.html>
2020 Jul 11
2
LLVM source compilation Error: CommandLine Error: Option 'mc-relax-all' registered more than once!
Dear All, Recently, I wanted to reinstall a fresh copy of llvm for a new project I am working on. However I ran into the following issue when attempting to build a vanilla copy. CommandLine Error: Option 'mc-relax-all' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options make[2]: ***
2020 Jul 10
5
CentOS 7 rsyslog and ELK
I asked a similar question about a year ago and didn't get any answers. So I thought I'd try again. What do people do to get their syslog messages on CentOS 7 into a remote ELK stack. I've tried lots of things involving rsyslog, filebeat, redis, logstash and so on in lots of different configurations but nothing really works. I can get rsyslog to talk directly to logstash (acting as
2020 Jul 11
4
Syncing emails from external server like Gmail
...ights that "Mailboxes are equal" but still verifies all the UIDs again. Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: dsync.log Type: text/x-log Size: 34257 bytes Desc: not available URL: <https://dovecot.org/pipermail/dovecot/attachments/20200711/cf850180/attachment-0001.bin>
2020 Jul 12
2
Emit LLVM bitcode after ThinLTO
...puts a bitcode file, but its file size is too small, and does not contain all contents. What is the correct way to emit LLVM bitcode after ThinLTO? Thank you, S -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200711/b3ef506e/attachment.html>
2020 Jul 09
3
question on analyzeBranch and getFallThrough
I am working on a back end for an architecture whose jump via table instruction includes the range check. If the index is out of range, the jump table instruction just falls through. I implemented a pass to remove the range check generated before the jump table instruction because it is superfluous. This causes as assertion in MachineBlockPlacement.cpp:
2020 Jul 11
0
[vhost:config-endian 33/36] drivers/vdpa/vdpa_sim/vdpa_sim.c:335:21: sparse: sparse: incorrect type in assignment (different base types)
...https://lists.01.org/hyperkitty/list/kbuild-all at lists.01.org -------------- next part -------------- A non-text attachment was scrubbed... Name: .config.gz Type: application/gzip Size: 32878 bytes Desc: not available URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20200711/3accae7c/attachment-0001.gz>
2020 Jul 10
2
RFC: Removing ptrtoint from asan instrumentation
[AMD Official Use Only - Internal Distribution Only] Hi everyone, Asan instrumentation introduces a ptrtoint instruction which is used as an argument to a number of runtime functions. Every instrumented load/store ends up having at least one ptrtoint attached to its address. However, the community has now raised a number of concerns about the use of LLVM generated ptrtoint & inttoptr [1]
2020 Apr 06
2
Branch is not optimized because of right shift
On Sun, Apr 5, 2020 at 6:34 PM Stefanos Baziotis < stefanos.baziotis at gmail.com> wrote: > Hi Craig, > > > Adding a nuw to the add -8 is incorrect. > Yeah, I didn't mean to say it was correct. It was just an observation that > with nuw the optimization was happened and I asked if someone thought it > was somehow connected. > > > From the perspective of the
2020 Jul 10
3
[cfe-dev] [RFC] Moving (parts of) the Cling REPL in Clang
On 7/10/20 1:57 PM, Vassil Vassilev wrote: > On 7/10/20 6:43 AM, JF Bastien wrote: >> I like cling, and having it integrated with the rest of the project >> would be neat. I agree with Hal’s suggestion to explain the design of >> what remains. It sounds like a pretty small amount of code. > > >   JF, Hal, did you mean you want a design document of how cling in >
2020 Jul 10
3
[cfe-dev] [RFC] Moving (parts of) the Cling REPL in Clang
Hi Richard, On 7/10/20 11:10 PM, Richard Smith wrote: > Hi Vassil, > > This is a very exciting proposal that I can imagine bringing important > benefits to the existing cling users and also to the clang user and > developer community. Thank you for all the work you and your team have > done on cling so far and for offering to bring that work under the > LLVM umbrella!