Hi Richard,
thank you very much for your suggestions, it seems to be working well.
Now, the temporary variables survive the SSA optimisations.
and the txn_save_* variables are optimised "away". Is there any way to
prevent this kind of optimisations on SSA form for a particular group of
variab
On 8/18/08 7:15 AM, Martin Schindewolf wrote:
txn_handle.12_4 = __builtin_stm_new ();
jmp_buf.13_5 = __builtin_stm_get_env (txn_handle.12_4);
ssj_value.14_6 = _setjmp (jmp_buf.13_5);
if (ssj_value.14_6 == 0)
goto ();
else
goto ();
# SUCC: 4 (false) 3 (true)
# BLOCK 3
# PRED: 2
On 8/15/08 1:00 PM, Martin Schindewolf wrote:
Hi all,
I currently introduce a temporary variable on SSA form but it
does not survive the SSA optimisation passes. (Not even the
simple ones triggered with -O1). Since the temporary variable
is considered to be a gimple register it is not possible t
GCC 4.3.2-rc1 is now available from
<ftp://gcc.gnu.org/pub/gcc/snapshots/4.3.2-RC-20080819>. 4.3 branch
remains in the state that all changes require release manager approval,
until 4.3.2 is released.
GCC 4.3.2 will follow in about a week in the absence of any significant
problems with
Hi folks.
Maybe the one or another remembers the post I've wrote more than a month
ago. I was (and still am) new to the GCC codebase and had the evil plan
to add an optimization pass to do byte permutations (capturing all
home-brewed bswap things and all the other 23 possible byte-permutations
On Wed, Aug 20, 2008 at 12:21:42AM +0200, Nils Pipenbrinck wrote:
> Well - I had a lot of time to kill during the last weeks, and I had a
> lot of timeto read into the source. Business trips without internet
> access are a perfect opportunity to read such stuf...
>
> Anyway, after all this passi
Balthasar Biedermann schrieb:
> I create a gcc-backend. I have already created the *.md, *.h and *.c
> files and I have compiled the gcc which includes backend.
>
> But when I try to compile a simple c-File with my gcc I get a
> Segmentation fault. I tried to debug it but I don't get the point.
>
> > The Error occures in mark_jump_label_1. It is called with a null pointer
> > as the rtx x.
>
> Does nobody have an idea why or where the error occures? I really start
> to became desperate.
I'm sure plenty of people have an idea of why the error occurs.
However, you need to be clearer in expl
