search for: refspec

...i_def_cfa_offset 128 Ltmp4: .cfi_offset %rbx, -16 Which does contain the rsp updates. The two places I can think with some documentation are http://www.dwarfstd.org/doc/DWARF4.pdf (the 6.4 Call Frame Information section). This is the old .debug_frame, but that is where the idea came from. http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/ehframechpt.html http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/dwarfext.html#AEN1154 Cheers, Rafael

Hi Rafael, I've been staring at the CFI directives and have a question. Some background: I want to generate the compact unwind information using just the CFI directives. I *think* that this should be doable. The issue I'm facing right now is that I need to know how much the stack pointer was adjusted. So when I have something like this: .cfi_startproc Lfunc_begin175:

In lib/gcc_personality_v0.c, I believe the type of the exception_cleanup member of the struct _Unwind_Exception is incorrect. It has a return type of _Unwind_Reason_Code versus a return type of void as specified in http://refspecs.freestandards.org/abi-eh-1.21.html, and as can be seen in unwind.h on Linux, and OS X 10.6.x (the latter's unwind.h is under the Developer directory tree). The attached patch changes this return type to void. Garrison -------------- next part -------------- A non-text attachment was scrub...

Dearest list, I am using dovecot with heartbeat-2 and I noticed that the init scripts in the Debian packages from http://xi.rename-it.nl/debian/ do not conform to the LSB standard: http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html E.g. the return code for "program is not running" is not 3. Is there is special reason for this? Cheers Jan -- MAX-PLANCK-INSTITUT fuer Radioastronomie Jan Behrend - Rechenzentrum -------------------------...

Hi, I'm recently trying to investigate ppc_fp128 related problem. Here is a minimal C++ test case that seems wrongly compiled: long double id(long double a) { return a; } bool f(long double x) { return id(__builtin_fabsl(x)) >= 0; } int main() { if (f(-123.l)) { return 0; } return 1; } The program compiled with command: clang++ -static -target powerpc64le-linux-gnu bad.cc

...-3. [ Remember, Solaris was the original GNU platform. ] So in that regard, Debian is actually like Solaris in its use of 2-3, instead of Fedora-based 3-5. Secondly, you are referring to Linux Standards Base (LSB). Specifically, Section 8.5 in the General Section of the latest revision: http://refspecs.freestandards.org/LSB_2.1.0/LSB-Core-generic/LSB-Core-generic.html#RUNLEVELS And even this latest version states: "However, it is not required that LSB-compliant run-time environments use these run levels; the distribution-provided install_initd script may map the run levels specified be...

On Sat, Jan 9, 2010 at 5:54 AM, Garrison Venn <gvenn.cfe.dev at gmail.com> wrote: > If the powers at be want this, I could easily transform the source to the LLVM coding standards, and add > the necessary portable UNIX support--someone else would have to add non-UNIX support although the > System library probably helps with this. However I'm guessing the LLVM release flux of the

Hi Jim, I didn't use any documents, but intensively looked at gcc's output. I think this document: http://refspecs.freestandards.org/elf/elfspec_ppc.pdf is the last specification of the ABI. Cheers, Nicolas Jim Laskey wrote: > Nicolas, > > Would you point me to the Linux/PPC ABI documents you are using so I > can better judge what your restrictions are? These changes also have > an effect...

If the powers at be want this, I could easily transform the source to the LLVM coding standards, and add the necessary portable UNIX support--someone else would have to add non-UNIX support although the System library probably helps with this. However I'm guessing the LLVM release flux of the exception system, along with a lack of universal platform, dwarf JIT support might be a hinderance in

On Mon, Nov 30, 2015 at 7:24 PM Gao, Yunzhong < yunzhong_gao at playstation.sony.com> wrote: > According to > http://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi.html, > "The high-order double-precision value (the one that comes first in > storage) must have the larger magnitude." > > So the order of the two doubles in your fp128 is not affected by the > endianness; although each individua...

I''ve been experiencing some odd behavior with puppet and checking the status of running processes. Let me see if I can explain it: I have a very simple node.js socket server I''m attempting to puppetize. It is managed through an init.d script with start, stop, status, and restart. The init.d script runs perfectly fine as any other user in the system. However, when puppet

...il recently, I thought that -O0 had this effect. - In each case, I would propose to not perform optimizations at -O0 to allow dynamic bug finding tools to find such bugs, or at least offer a flag to turn off optimizations altogether. [1] https://github.com/google/sanitizers/issues/773 [2] https://refspecs.linuxfoundation.org/LSB_2.0.1/LSB-Core/LSB-Core/baselib---ctype-b-loc.html -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170321/2f5806d4/attachment.html>

I notice that many DAG nodes like the copy-to-register operation have the ability to take an optional flag parameter, but that the load/store nodes do not (at least as of 2.3). Is it possible to pass flag operands through load/store DAG nodes?

On Nov 17, 2008, at 11:12 AM, Burke, Max wrote: > I notice that many DAG nodes like the copy-to-register operation have > the ability to take an optional flag parameter, but that the load/ > store > nodes do not (at least as of 2.3). Is it possible to pass flag > operands > through load/store DAG nodes? No there isn't. What are you trying to accomplish? Are you trying to

Erik, It turns out bc(1) is too accurate, and a little slow, for this purpose. I've switched to using awk(1) which uses floating point. Do you feel I need to test for the presence of awk(1) ? It is specified as one of the standard commands in the LSB : http://refspecs.linuxfoundation.org/LSB_1.0.0/gLSB/command.html Earl ??? awk -- ' ??? BEGIN { ??????????? samplerate = 8000; ??????????? tone = 1000; ??????????? duration = 1; ??????????? bitspersample = 24; ??????????? samplemidpoint = lshift(1, (bitspersample-1)); ??????????? samplerange = samplemidpo...

Hi Timo, please find attached a patch for the init script in the doc directory. * Added LSB-compliant info block (for insserv and friends) * Updated base_dir detection (for v2.0 config output) Regards, Pascal -- The trapper recommends today: decade.0932307 at localdomain.org -------------- next part -------------- A non-text attachment was scrubbed... Name: dovecot-initd_LSB_header.patch

Hello list, I would add: # dovecot Startup script for the dovecot server # # chkconfig: - # processname: dovecot # config: /path/to/config # pidfile: /path/to/pid So that it supports the chkconfig used by RHEL and clones too. Also, maybe it should be installed by the Makefile's install target? it could then also set: DAEMON=/path/to/dovecot/daemon instead of:

Here are the items removed when removing postfix: Nov 1 09:56:59 localhost yum[22042]: Erased: google-chrome-stable Nov 1 09:57:00 localhost yum[22042]: Erased: redhat-lsb-compat Nov 1 09:57:00 localhost yum[22042]: Erased: redhat-lsb Nov 1 09:57:01 localhost yum[22042]: Erased: redhat-lsb-graphics Nov 1 09:57:01 localhost yum[22042]: Erased: redhat-lsb-printing Nov 1 09:57:02 localhost

...a va_list in these architectures is just a pointer to the stack. The va_start intrinsic just initializes where the pointer points at in the stack. I do not know how the other backends operate, but I suppose it's the same. However, on the PPC/ELF ABI, a va_list is a struct (referring to http://refspecs.freestandards.org/elf/elfspec_ppc.pdf) of 12 bytes allocated on stack. The struct *should* not be allocated by va_start because a va_copy would not know if the struct is allocated or not. Therefore, I think there should be a special intrinsic for declaring a va_list. This unfortunately requires c...

Dear all, AFAIK, ARM EHABI is not ready for both asm and obj emitter. Some people including me what to implement them. My question is, to avoid duplicate effort, does someone take charge of this part? or does anyone is already implementing this currently? BTW, any suggestion on this effort? I'm very appreciated! Thanks in advance! -- Best regards, Wen-Han Gu (Nowar) -------------- next