similar to: ssh ignores -f with protocol version 2

Here's a patch to fix some bugs in my code, plus a header file I probably forget to send in before. * Missing header file charset.h. It's not needed outside vorbis-tools/share, so I think it can live there. * There was a minor bug in the UTF-8 decoder utf8_mbtowc(). * I've added some more tests in charset_test.c in an attempt to convince myself that there aren't any more bugs.

2010/1/25 Edmund Grimley Evans <Edmund.Grimley-Evans at arm.com>: > I just got this error message from the GNU assembler: > > Error: alignment too large: 15 assumed > > Which made me laugh at first. The corresponding input line was: > >        .align  16 > > Apparently what's going on here is that ".align 16" is ambiguous: on > some architectures

Here's a propsed heavy-duty solution for your UTF-8 problems. I'm including a patch in this message, but I'll put the new files on my web site at http://rano.org/tmp/xiph_files.tar.gz I've tested this by running vorbiscomment with and without -DHAVE_ICONV=1 in vorbis-tools/share/Makefile. It seems to work. Changed files: acinclude.m4: Add a test for nl_langinfo(CODESET). This

Assuming you're working with an ARM target, you may also hit a problem with the alignment option on the .comm directive. Attached is a first-cut patch for this latter problem. deep On Mon, Jan 25, 2010 at 5:42 PM, Edmund Grimley Evans <Edmund.Grimley-Evans at arm.com> wrote: > I just got this error message from the GNU assembler: > > Error: alignment too large: 15 assumed

On Tue, 14 Dec 2010 10:55:09 -0000 "Edmund Grimley-Evans" <Edmund.Grimley-Evans at arm.com> wrote: > According to the few tests I did, .ll.gz is more compact: > > 1.00 LLVM bitcode (.bc) > 0.80 Gzipped LLVM bitcode (.bc.gz) > 4.13 LLVM assembly (.ll) > 0.68 Gzipped LLVM assembly (.ll.gz) > > However, there's not much in it, considering that a

I just got this error message from the GNU assembler: Error: alignment too large: 15 assumed Which made me laugh at first. The corresponding input line was: .align 16 Apparently what's going on here is that ".align 16" is ambiguous: on some architectures it means ".balign 16", and on some it means ".p2align 16", which would mean ".balign 65536" if

According to the few tests I did, .ll.gz is more compact: 1.00 LLVM bitcode (.bc) 0.80 Gzipped LLVM bitcode (.bc.gz) 4.13 LLVM assembly (.ll) 0.68 Gzipped LLVM assembly (.ll.gz) However, there's not much in it, considering that a stripped native binary is about 0.40 on the same scale. So, seeing as projects such as PNaCl want to send LLVM bitcode over the network, are there any proposed

I don't think this has ever worked. Evan On May 13, 2010, at 10:03 AM, Edmund Grimley-Evans wrote: > I think this test case demonstrates it: > > ; RUN: llc -march=thumb -mcpu=cortex-a8 -mtriple=thumbv7-eabi -float-abi=hard < %s | FileCheck %s > > define <4 x i64> @f_4_i64(<4 x i64> %a, <4 x i64> %b) nounwind { > ; CHECK: vadd.i64 > %y = add <4

It used to. I just checked with r90370. deep On Thu, May 13, 2010 at 11:53 PM, Evan Cheng <evan.cheng at apple.com> wrote: > I don't think this has ever worked. > > Evan > > On May 13, 2010, at 10:03 AM, Edmund Grimley-Evans wrote: > >> I think this test case demonstrates it: >> >> ; RUN: llc -march=thumb -mcpu=cortex-a8 -mtriple=thumbv7-eabi

Hi all, I added -Wmissing-prototypes -Wstrict-prototypes to the CFLAGS and found that there were a number warnings generated. The patch below fixes those warnings and adds the two -W flags to configure.in. Cheers, Erik ----------------------8<----------------------8<---------------------- --- src/metaflac/operations_shorthand.h 1970-01-01 00:00:00 +0000 +++

Hello ! Like Edmund EVANS reported openssh-2.1.1p4 won't fork to background when using protocol 2. I managed to hack a little patch that might work ... What is the -N command line option supposed to do ? I gather it should work only with protocol2 and without any command to run on the server (and with some port forwardings ??) Anyway in the patch I put some code to check that -N is used

The log message for revision 122213 says: > Change the X86 backend to stop using the evil ADDC/ADDE/SUBC/SUBE nodes (which > their carry depenedencies with MVT::Flag operands) and use clean and beautiful > EFLAGS dependences instead. (MVT::Flag has since been renamed to MVT::Glue.) That revision made bug 8404 go away. Am I right in thinking that one of the problems with MVT::Glue is

Could some kind soul point me at the documentation, or the appropriate header file, or an example of the best way to write a pass that modifies the IR? Suppose, for example, that I wanted to replace every call to the intrinsic i1 with a call to i2 followed by a call to i3: i1(X) -> i3(i2(X)) I'm currently playing around with a class that inherits from FunctionPass and InstVisitor and I

You forgot to reply to the list. Also CC'ing LLVMdev. On 3/12/10 1:41 PM, Edmund Grimley-Evans wrote: >>> clang -cc1 -triple thumbv7-eabi -O3 -target-cpu cortex-a8 t.c >>> -emit-llvm-bc >>> llc t.bc ... -view-legalize-dags >> You just answered your own question :). That will work quite nicely >> actually. > > Maybe it would if I knew exactly what

Ok, please file a bug. Evan On May 13, 2010, at 6:23 PM, Sandeep Patel wrote: > It used to. I just checked with r90370. > > deep > > On Thu, May 13, 2010 at 11:53 PM, Evan Cheng <evan.cheng at apple.com> wrote: >> I don't think this has ever worked. >> >> Evan >> >> On May 13, 2010, at 10:03 AM, Edmund Grimley-Evans wrote: >>

Having a look at clang's source, you can find in "lib/CodeGen/BackendUtil.cpp" the functions where clang builds the passes to emit code. The optimization passes used are there and you can simulate them via the "opt" utility, by running each pass one at a time. LLVM also declares standard module/function passes on include/llvm/Support/StandardPasses.h. Have a look and see

I'm getting a lot of this from make check: g++: unrecognized option `-Qunused-arguments' This presumably comes from commit 94666 (test/LLVMC/ExternOptions.td and other files). That option is specific to clang, isn't it? Should %compile_cxx be picking up clang instead of my system's g++? -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and

I think this test case demonstrates it: ; RUN: llc -march=thumb -mcpu=cortex-a8 -mtriple=thumbv7-eabi -float-abi=hard < %s | FileCheck %s define <4 x i64> @f_4_i64(<4 x i64> %a, <4 x i64> %b) nounwind { ; CHECK: vadd.i64 %y = add <4 x i64> %a, %b ret <4 x i64> %y } (I hope I got that right.) -- IMPORTANT NOTICE: The contents of this email and any

James, many thanks. Is there any linker available for Macs that has a freely available binary version? I thought maybe that GNU’s linker might fit the bill? I cannot use Apple’s linker from /usr/bin/ as it is not allowed to make external calls from a sandboxed app. Hence my interest in the LLVM lld. > On 7 May 2020, at 19:21, James Y Knight <jyknight at google.com> wrote: > > On

Hi, I'm using samba-2.0.6-19991110 on Redhat 6.1 in order to mount a NT-filesystem. The mount command is: smbmount //ISDN/CoTel /mnt/NT-Bank/ -o username=serv,password=serv,workgroup=WORK,uid=root,gid=users,ro everything works fine, except that after one or two days the mount disappears. A simple 'ls /mnt/NT-Bank/MCCWIN' results in 'Input/output error'. In