Re: [Chicken-hackers] Half a bug report

[Christian Kellermann]

* Jörg F. Wittenberger <address@hidden> [120605 23:11]:
> That's been my point: as soon as I remove enough of the actual
> code to pin down the problem, everything is fine.
>
> To be clear my timeline step wise:
> 1. new (May) compiler on bad complex source compiled without
>   warning into bad code.  (Several compiler rebuilds
>   and different machines.)
>   [[Me so far no idea why.]]
> 2. Reverting to old (Feb) version gave immediately the warning
>   about wrong parameter; not completing the compile.
> 3. Fixed the call both compilers produce good code.
>   [[issue at hand solved now prepare the report]]
> 4. Try to boil the bad code into foo/bar -> hardly compiles
>   until all "unrelated" stuff is removed.  Eventually all
>   appears to be more related than hoped for.  Once short like
>   that May compiler catch the error too.
>
> But don't aim chicken on the above example.  It works.
> That is, it complains rightfully.

Then I can only give the same advice that doctors give when on their
wits' end: Please observe the further development of the patient's
health.

Thanks for the heads up! At the moment I don't now how to track this
further down on my end though...

Kind regards,

Christian

--
9 out of 10 voices in my head say, that I am crazy,
one is humming.