Hello all,
Apologies in advance if this question is naïve or misdirected.
tl;dr: Is dividing by INT64_MIN in C undefined behaviour?
In more detail... AIUI when the current target does not have native instructions for a given division or modulo
operation, GCC emits calls to software emulation p
Snapshot gcc-6-20151004 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20151004/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
On 4 October 2015 at 10:50, mads_bn wrote:
> Can somebody try if e.g. backtrace_symbols () will show where the offending
> code was called from?
Included a backtrace test, pushed to github.
./test(_Z9backtracev+0xb)[0x10f28]
./test(_Z17backtrace_handleri+0x5)[0x10f4a] < signal handler
./
On 4 October 2015 at 10:05, Andrew Haley wrote:
> Do you have GCC copyright assignment
No, but I hereby license it under the http://www.wtfpl.net/ (or, in
any legal system which acknowledges such an act, place it in public
domain)
> will you turn this into a patch which can be applied?
I've alr
Nice work !
Some time ago I was in a project, where we would like to get more context in
syslog when e.g. SIGSEGV occurred (embedded Linux).
On x86 this was working fine, and I hope a change like this for ARM will
allow it to work here as well (as long as stack is still valid).
I don't hav
On 03/10/15 21:41, Matthijs van Duin wrote:
> Anyhow, it only took four years, but you can now throw
> NullPointerExceptions on ARM. Enjoy. ;-)
Ok, nice. :-)
Do you have GCC copyright assignment, and will you turn this into
a patch which can be applied?
Thanks,
Andrew.
