Displaying 20 results from an estimated 23 matches for "20201116".
Did you mean:
20101116
2020 Nov 15
10
[Bug 1483] New: v0.9.7 does not compile for arm-linux-gnueabihf
https://bugzilla.netfilter.org/show_bug.cgi?id=1483
Bug ID: 1483
Summary: v0.9.7 does not compile for arm-linux-gnueabihf
Product: nftables
Version: unspecified
Hardware: arm
OS: Debian GNU/Linux
Status: NEW
Severity: blocker
Priority: P5
Component: nft
Assignee: pablo at
2020 Nov 15
1
[Bug 1484] New: configure script fails to detect python3
https://bugzilla.netfilter.org/show_bug.cgi?id=1484
Bug ID: 1484
Summary: configure script fails to detect python3
Product: nftables
Version: unspecified
Hardware: x86_64
OS: Debian GNU/Linux
Status: NEW
Severity: normal
Priority: P5
Component: nft
Assignee: pablo at
2020 Nov 16
0
Analyze SCEV expression after IR is removed clarification
...yzed through" is removed then I would argue that the SCEV expression should still be analyzable.
Thoughts, comments and clarifications are welcome.
-Markus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201116/18c3cf2b/attachment.html>
2020 Nov 16
1
Support request Icecast
...ast problems?
I am getting a bit confused by the whole contact scheme provided on the
website If not please let me know.
Kind regards,
Steven Moser
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast-dev/attachments/20201116/b3f6593d/attachment.html>
2020 Nov 16
1
help with "too many clients awaiting authentication"
Hello guys,
Today we faced an unique problem.
We have about 120 stations and we are reaching 40k simultaneous listeners monday/friday (~ 11 AM GMT -3).
We also use url auth to log, audit and build audience reports.
But today, at the end of the day we were about 10k simultaneous and listeners start get errors (403, busy, please try again later), and after digging, delete logs and restart
2020 Nov 13
5
[Bug 1481] New: [ebtables-nft] ebtables -E gives error
https://bugzilla.netfilter.org/show_bug.cgi?id=1481
Bug ID: 1481
Summary: [ebtables-nft] ebtables -E gives error
Product: iptables
Version: unspecified
Hardware: x86_64
OS: Debian GNU/Linux
Status: NEW
Severity: normal
Priority: P5
Component: iptables
Assignee:
2020 Nov 17
3
Notes from GitHub Pull Requests round table
I saw some other posts on this list about notes from the round tables at
the conference. Did anyone take some for the GitHub round table?
Thanks!
--
Keith Smiley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201116/449e0980/attachment.html>
2020 Nov 17
0
Renaming The Default Branch
..._____________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201116/8b2ffa1c/attachment-0001.html>
2020 Nov 17
0
Renaming The Default Branch
...________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201116/cf2ce163/attachment.html>
2020 Nov 12
2
LLVM X86 MachineBasicBlock inserting push and pop instructions causes segmentation fault
Hello,
I am working on a project where I need to insert some logic before each
machine basic block.
In particular, it involves setting some global variables and calling a
function. I'm able to add the instructions and verify they get added, but
when the compiled program runs, it stops with a segfault.
For brevity, I'm not sharing the whole code here but basically I have a X86
2020 Nov 16
2
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...______________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201116/bdc38d10/attachment.html>
2020 Nov 16
2
ORC JIT Weekly #26 -- Orc library break-up, remote TargetProcessControl, and the beginnings of a runtime.
...g/pipermail/llvm-dev/2020-September/145070.html
[3] https://github.com/lhames/llvm-project/tree/orc-runtime-prototype
[4] https://llvm.org/docs/ORCv2.html#roadmap
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201116/c41788e3/attachment.html>
2020 Nov 17
4
RFC: Contributing Bazel BUILD files in the "peripheral" support tier
...contribution will significantly improve the situation for
downstream users that use Bazel while having minimal impact on the
community at large.
Thanks,
Geoffrey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201116/22a3b454/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3992 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201116/22a3b454/attachme...
2020 Nov 17
2
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...pers mailing list
> >> >> > llvm-dev at lists.llvm.org
> >> >> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201116/119b711e/attachment.html>
2020 Oct 12
3
MemorySSA LLVM-dev meeting notes and upcoming meetings
Hello,
Following up on last week's LLVM-Dev meeting where we discussed MemorySSA
related topics, I created the following google doc
<https://docs.google.com/document/d/1-uEEZfmRdPThZlctOq9eXlmUaSSAAi8oKxhrPY_lpjk/edit#>
with some of the meeting notes and planning for future meetings. For those
who participated, please feel free to add items I may have missed into the
document and cc
2020 Nov 17
1
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...t;> >> > llvm-dev at lists.llvm.org
>>> >> >> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201116/3b93a2ad/attachment.html>
2020 Nov 16
2
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...; > LLVM Developers mailing list
> >> > llvm-dev at lists.llvm.org
> >> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201116/37c6bee4/attachment-0001.html>
2020 Nov 14
2
Renaming The Default Branch
On Fri, Nov 13, 2020 at 4:53 PM James Y Knight via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> I notice that on https://github.com/github/renaming it says:
>
> """If you haven’t renamed your default branch yet, consider waiting until later
> this year <https://github.com/github/renaming#later-this-year>. We’re
> investing in tools to make renaming the
2020 Nov 17
0
RFC: [SmallVector] Adding SVec<T> and Vec<T> convenience wrappers.
...>> >> >> > llvm-dev at lists.llvm.org
>> >> >> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201116/8ae25c3b/attachment-0001.html>
2020 Nov 17
2
Renaming The Default Branch
This timing actually is likely to be more convenient for my downstreams, as most of the devs will be away.That way we can ‘ease’ into our transition with a limited number of devs being affected by it…
That said, from a downstream-perspective, it looks like we’ll still be keeping ‘master’ updated for a while, right?
> We will lock the master branch and change it to be readonly (with the