similar to: Determine reason for failure at -O1

We have code that processes a buffer in the forward or backwards direction. It looks similar to the following (https://github.com/weidai11/cryptopp/blob/master/adv-simd.h#L1138): uint8_t * ptr = ... size_t len = ... size_t inc = 16; if (flags & REVERSE_DIRECTION) { ptr += len - inc; inc = 0-inc; } while (len > 16) { // process blocks ptr += inc; len -= 16; } Clang

HI, When compiling the open-source software cryptopp (https://www.cryptopp.com/#download <https://www.cryptopp.com/#download>) version 5.6.4 I found a strange issue with the IR generated. The issue only appears when compiling with -O2 optimisation in the integer.cpp file (the function is _ZN8CryptoPPrsERNSt3__113basic_istreamIcNS0_11char_traitsIcEEEERNS_7IntegerE ->

Hi, I'm a PhD student and I want to use the function 'daisy' from the package 'cluster' to compute dissimilarities. My variables are of mixed types so I use the argument 'stand' in daisy to define the type of my variables. I have the following error message : Warning message: binary variable(s) 13, 16, 17, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35,

I'm testing on older OS X 10.8 with older SSE4 hardware from about 2010. I've got updated gear from MacPorts and it includes GCC and Clang. GCC is the compiler, and Clang is the assembler. We perform a compile/link on a test file to ensure an ISA is supported by the toolchain. If an ISA is available then we compile a source file to the ISA as needed. Then, we guard the higher ISAs at

Hi, I just tried to build using http://dl.fedoraproject.org/pub/epel/6/SRPMS/pdns-3.1-2.el6.src.rpm on CentOS 6.4 final (kernel: 2.6.32-358.2.1.el6.x86_64), but it failed when looking for ldap libs: Note: I did not change anything in the original spec file. ... + ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu

Erik de Castro Lopo wrote: > When should FLAC__HAS_X86INTRIN be defined? What header file should I be > checking for? Ah, should be checking for <x86intrin.h>. The rest seems to be coming together. Testing this now. Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

I have a search form on my rails site. once the a user has entered a query it displays the results in a table with an extra field button so it can be added to there own portfolio called add to my stocks. How do i get the data for the stock they want to add and put this into a new table called mystocks. Is using a form submit button the right choice? Any examples much appreciated Regards Nick

Hello, I try to recompile syslinux-4.00 pre31 on RHEL5 with gcc-4.1.2 and nasm 2.07. Because I'm looking for information about that gpxelinux->chain.c32 hd0 boot problem I added -DDEBUG=2 to com32/lib/Makefile I get: objdump -h pxelinux.elf > pxelinux.sec perl lstadjust.pl pxelinux.lsr pxelinux.sec pxelinux.lst objcopy -O binary pxelinux.elf pxelinux.raw ../lzo/prepcore

Hello, I have been struggling to do a plot in ggplot(2) that's of lattice equivalent. The following code shows the lattice plot.

On Tue, Apr 14, 2015 at 03:20:08PM -0400, Gene Cumm wrote: > > I thought I would try to find out how pxelinux copes with this, by trying > > to insert printfs in pxe_init, but nothing gets printed. > > This is normal. Can you give me hint as to why setting > > DEBUGOPT = -DDEBUG=1 -DDEBUG_STDIO -DCORE_DEBUG=1 changes that state of normality? (AFAICT dprintf.h

> Speaking of CFLAGS, it looks like configure.in clobbers any existing > CFLAGS in > the environment. This can be a pain when trying to compile with a > modified > CFLAGS, as the usual idiom is: > > CFLAGS=... ./configure ... > > thus propagating CFLAGS to all generated makefiles. The right thing > to do is > probably to prepend to CFLAGS instead of replacing

I have reason to believe that an odd box that is having boot trouble has three instances of "!PXE" in the chunk of memory that "Method D" should look at. I thought I would try to find out how pxelinux copes with this, by trying to insert printfs in pxe_init, but nothing gets printed. I can spew lots of output if I set DEBUGOPT = -DDEBUG=1 -DDEBUG_STDIO -DCORE_DEBUG=1 but

The sed expression is wrong, any flags with '-g' in any position gets zapped, for example: -mfloat-gprs=double (for powerpc e500) -> -mfloatprs=double. Which gives build errors and is perfectly valid in real use scenarios to switch from e500v1 (single precision) code to e500v2 (double precision) code. Signed-off-by: Gustavo Zacarias <gustavo at zacarias.com.ar> ---

I have several related questions. 1. Is it possible to use a GUI: Rstudio/Eclipse/Visual-studio to debug compiled code on Windows? Things that work on Eclipse for Windows do not work on Eclipse for Windows. 2. R CMD INSTALL seems to override default attempts to provide CFLAGS="-DDEBUG -g3 -O0" 3. Is it necessary to compile R with debug turned on? One of the FAQs mentioned to

On Fri, Jul 12, 2013 at 2:21 AM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/11/2013 10:16 PM, Raphael S.Carvalho wrote: >> This patch adds support for serial output functions. >> It may be useful for debugging purposes since you can separate ordinary outputs from debugging dumps. >> Just add "serial.h", and use either serial_print or serial_puts as you

I'm considering the suggestion which was raised before about turning the debugging messages on by default in isolinux, or specifically, not building the non-debugging-messages version in the standard distribution. What do people think (especially distro maintainers?) -hpa

I need to use a cryptography library extension for C/C++ and I'd like to know if anyone can tell me wich one on ports collection is better (the most complete and "easy" to use). Is there anyway to use MIRACL on FreeBSD(and how)?

Why are legacy MACs (like md5-96), and legacy Ciphers (anything in cbc-mode, arcfour*(?)) enabled by default? My proposal would be to change the defaults for ssh_config and sshd_config to contain: MACs hmac-sha2-256,hmac-sha2-512,hmac-sha1 Ciphers aes128-ctr,aes192-ctr,aes256-ctr ...removing md5, truncated versions of sha1, umac64 (for which I can find barely any review), any cipher in cbc

Sorry if I''m just dumbing out, but is there a reason that when using Single Table Inheritance Rails doesn''t really validate the "type" field or provide some mechanism to do so? seems like a good way to corrupt a database. Because the "type" is also a special attribute, I had to resort to an ugly hack like: class ActiveRecord::Base def type_attr

Anyone else getting this when building the latest mesa? make[3]: Entering directory `/usr/local/nouveau/mesa2/mesa/src/gallium/targets/dri-nouveau' gcc -c -I. -I../../../../src/mesa/drivers/dri/common -Iserver -I../../../../include -I../../../../include/GL/internal -I../../../../src/mapi -I../../../../src/gallium/include -I../../../../src/gallium/auxiliary