similar to: Interpreting Asterisk Logs

IM 2013 The 13th IFIP/IEEE Symposium on Integrated Network and Service Management Ghent, Belgium, 27-31 May 2013 http://www.im2013.org/ (Paper Submission Date: 16 August 2012) "Smart Management in a Virtualized World" The 13th IFIP/IEEE Symposium on Integrated Network and Service Management (IM 2013) will be held 27-31 May 2013 in the beautiful city center of Ghent, Belgium and

IM 2013 The 13th IFIP/IEEE Symposium on Integrated Network and Service Management Ghent, Belgium, 27-31 May 2013 http://www.im2013.org/ (Paper Submission Date: 16 August 2012) "Smart Management in a Virtualized World" The 13th IFIP/IEEE Symposium on Integrated Network and Service Management (IM 2013) will be held 27-31 May 2013 in the beautiful city center of Ghent, Belgium and

----- Original Message ----- > From: "Reid Kleckner" <rnk at google.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "Chris Lattner" <clattner at apple.com>, "llvm-dev" <llvm-dev at lists.llvm.org>, "ジョウェットジェームス" > <b3i4zz1gu1 at docomo.ne.jp> > Sent: Monday, October 31, 2016 11:39:04 AM > Subject:

----- Original Message ----- > From: "Chris Lattner via llvm-dev" <llvm-dev at lists.llvm.org> > To: "David Chisnall" <David.Chisnall at cl.cam.ac.uk> > Cc: llvm-dev at lists.llvm.org, "ジョウェットジェームス" <b3i4zz1gu1 at docomo.ne.jp> > Sent: Friday, October 28, 2016 2:13:06 PM > Subject: Re: [llvm-dev] What was the IR made for precisely?

I think it would be possible to build a stripped-down C-with-extensions-only type representation that represents only the types that have interesting ABI implications. This includes several things not present in LLVM IR types: _Complex, union, flexible array members, alignment attributes, etc. We could either then use that library to generate LLVM IR, or embed it in the IR for use at call sites.

On 28 Oct 2016, at 02:43, ジョウェットジェームス <b3i4zz1gu1 at docomo.ne.jp> wrote: > > I would need to sum up all the rules and ABIs and sizes for all the targets I need and generate different IR for each, am I correct? This is a long-known limitation of LLVM IR and there are a lot of proposals to fix it. It would be great if the LLVM Foundation would fund someone to do the work, as it

> On Oct 28, 2016, at 1:21 AM, David Chisnall via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 28 Oct 2016, at 02:43, ジョウェットジェームス <b3i4zz1gu1 at docomo.ne.jp> wrote: >> >> I would need to sum up all the rules and ABIs and sizes for all the targets I need and generate different IR for each, am I correct? > > This is a long-known limitation of LLVM IR

On 28 Oct 2016, at 09:46, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> On Oct 28, 2016, at 1:21 AM, David Chisnall via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> On 28 Oct 2016, at 02:43, ジョウェットジェームス <b3i4zz1gu1 at docomo.ne.jp> wrote: >>> >>> I would need to sum up all the rules and ABIs and sizes for all the targets I need

CONFIG_PHYSICAL_ALIGN gives the physical address's alignment where the kernel is loaded. CONFIG_PHYSICAL_ALIGN's default value is different from i386 kernel with the x86_84 kernel. The i386's default CONFIG_PHYSICAL_ALIGN value is 1MB, but the x86_64's is 2MB. The problem is, if you compile x86_64 kernel, the value of CONFIG_PHYSICAL_ALIGN will be fixed, and the next time you

CONFIG_PHYSICAL_ALIGN gives the physical address's alignment where the kernel is loaded. CONFIG_PHYSICAL_ALIGN's default value is different from i386 kernel with the x86_84 kernel. The i386's default CONFIG_PHYSICAL_ALIGN value is 1MB, but the x86_64's is 2MB. The problem is, if you compile x86_64 kernel, the value of CONFIG_PHYSICAL_ALIGN will be fixed, and the next time you

Halo, Is mirror to get 2.2.9? cannot get dovecot.org, this time out 4 xe-0-1-0-1-3664.r00.saplbr01.br.bb.gin.ntt.net (200.15.0.45) 6.946 ms 7.093 ms 6.899 ms 5 xe-4-1-3.r20.miamfl02.us.bb.gin.ntt.net (129.250.3.217) 118.130 ms 118.111 ms 118.117 ms 6 ae-1.r05.miamfl02.us.bb.gin.ntt.net (129.250.2.185) 118.592 ms 118.735 ms 118.628 ms 7 * * * 8 * * * 9 * * * I use to get from

Hi everyone! I'm wondering if anyone on the list had the opportunity to work with an NTT INS1500 ISDN PRI service before. You see, in Japan, if you receive a call that was just forwarded by another number, the call presentation not only includes the caller (ANI) and your number (DNIS), it will also usually include the forwarding number (REDIRECT). Does anybody know how to extract this field

On 28 Oct 2016, at 10:10, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> On Oct 28, 2016, at 1:59 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: >> >> On 28 Oct 2016, at 09:46, Mehdi Amini <mehdi.amini at apple.com> wrote: >>> >>>> On Oct 28, 2016, at 1:21 AM, David Chisnall via llvm-dev <llvm-dev at

> On Oct 28, 2016, at 1:59 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > > On 28 Oct 2016, at 09:46, Mehdi Amini <mehdi.amini at apple.com> wrote: >> >>> On Oct 28, 2016, at 1:21 AM, David Chisnall via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> On 28 Oct 2016, at 02:43, ジョウェットジェームス <b3i4zz1gu1 at

Hi. When I compiled xen-3.3-testing with DEBUG_TRACE_DUMP in xen/include/xen/lib.h turned on, I got some errors at SHADOW_PRINTK. The following patch will fix the arguments passed to SHADOW_PRINTK in xen/arch/x86/mm/shadow/common.c and xen/arch/x86/mm/shadow/multi.c. Although I haven''t tested, it is the same for xen-unstable.hg Thanks, Yoshi Signed-off-by: Yoshi Tamura

Whenever I review audit logs, it is difficult for me to determine if an account was logged in at an usual day/time because there is no timestamp next to any entry, at least as I interpret the format. How, then do I properly and successfully review the audit log entries based on a date/time stamp? Also, how can I filter out root and sudo account entries, displaying everyone else in audit?

Thanks to everyone for a fruitful discussion, links and ideas. The result is nearing a merge at https://github.com/networkupstools/nut/pull/2013 and seems to not upset CI on any platform, including Windows (which behaves funny WRT binding to the same host:port as many times as you ask). Ultimately the chosen logic is that if there was a `LISTEN * <port>` in `upsd.conf`, the depending on

Thanks to everyone for a fruitful discussion, links and ideas. The result is nearing a merge at https://github.com/networkupstools/nut/pull/2013 and seems to not upset CI on any platform, including Windows (which behaves funny WRT binding to the same host:port as many times as you ask). Ultimately the chosen logic is that if there was a `LISTEN * <port>` in `upsd.conf`, the depending on

> On Oct 28, 2016, at 1:21 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > > On 28 Oct 2016, at 02:43, ジョウェットジェームス <b3i4zz1gu1 at docomo.ne.jp> wrote: >> >> I would need to sum up all the rules and ABIs and sizes for all the targets I need and generate different IR for each, am I correct? > > This is a long-known limitation of LLVM IR and

Anyone configured a E1 PRI in Kuala Lampur, Malaysia with TM Malaysia? What signaling did they provide, framing, formatting? primary-4ess Lucent 4ESS switch type for the U.S. primary-5ess Lucent 5ESS switch type for the U.S. primary-dms100 Northern Telecom DMS-100 switch type for the U.S. primary-dpnss DPNSS switch type for Europe primary-net5 NET5 switch type for UK,