Hello GCC and Clang devs!
Unlike the traditional approach of installing system libraries into one
central location like /usr/{lib,include}, the nix package manager [1]
installs each package into it's own prefix
(e.g. /nix/store/mn9kqag3d24v6q41x747zd7n5qnalch7-zlib-1.2.8-dev). Moreover,
each packa
On 10/15/2016 08:41 PM, Segher Boessenkool wrote:
Hi Daniel,
On Sat, Oct 15, 2016 at 01:45:12AM -0500, Daniel Santos wrote:
The insn that's getting deleted is 75, where RCX is set. I'm starting
to think that maybe df_analyze() presumes that my call (to the stub) is
invalidating RCX, although i
On Sun, Oct 16, 2016 at 05:05:17PM -0500, Daniel Santos wrote:
> >>The insn that's getting deleted is 75, where RCX is set. I'm starting
> >>to think that maybe df_analyze() presumes that my call (to the stub) is
> >>invalidating RCX, although it does not.
> >It looks like you don't use add_functi
Snapshot gcc-7-20161016 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20161016/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
On 10/16/2016 05:27 PM, Segher Boessenkool wrote:
Oddly enough, I had forgotten to call add_function_usage_to() on my save
stub (which I didn't post), but not the restore stub. So thanks for that
psychic intervention. :) But if you look carefully, it's there, although
it's hard to read because
Hello,
Someone played with the GCC Bugzilla git repo last week with no real reason:
Author: root
Date: Fri Oct 7 15:28:43 2016 +
snap-data
Looks like the goal was to drop all CSS and JS files in data/assets/.
Why? There is no reason to play with the data/ directory. This directory
c
Hi there,
I come up with an idea about implementing stack unwinding for
the i686-w64-mingw32 target using native Windows Structured
Exception Handling (a.k.a SEH) for efficiency reasons.
Unlike DWARF and SEH for x64, SEH for x86 is stack-based
and works like the SJLJ exception model: The operatin
I think I've finally found the problem. It would appear that if you do
not explicitly add a note of type REG_CALL_DECL that specifies the
function declaration then it will ignore whatever you've supplied with
add_function_usage_to(). Instead, it will replace it with the target's
default regist
