e removed code, so
I don't really understand what you gain by closing bugs? Is it important
to keep the number of open issues low?
I don't consider bug reports a bad thing, they document the code quality
and are a useful resource to anyone working on the code or using these
versions.
Adria
> misleading.
If you don't accept my opinion, why did you ask for it in the first place.
Please do whatever you want. I will still continue to contribute to GCC
and start BountySource campaigns to support, despite my opinion not being
of any relevance.
Thanks,
Adrian
--
.''`. Joh
you are reducing the
number of open bug reports and you can somehow claim you fixed a bug.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
9-avr-convert-the-backend-to-mode_cc-so-it-can-be-kept-in-future-releases
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Hi!
On 5/25/20 2:56 PM, John Paul Adrian Glaubitz wrote:
>> I'm thinking about attempting to do the CC0 transition for the
>> AVR port in my spare time. I've read the CC0Transition gcc wiki
>> page, and as the AVR ISA does not have non-condition-code
>>
https://www.bountysource.com/issues/84630749-avr-convert-the-backend-to-mode_cc-so-it-can-be-kept-in-future-releases
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0
fo.td#L151
> [4] https://github.com/gcc-mirror/gcc/blob/master/gcc/config/m68k/m68k.h#L741
> [5]
> https://github.com/M680x0/M680x0-mono-repo/blob/master/llvm/lib/Target/M680x0/M680x0RegisterInfo.td
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub
Hi Nathan!
On 9/29/20 7:58 PM, Nathan Sidwell wrote:
> On 9/29/20 11:22 AM, John Paul Adrian Glaubitz wrote:
>>
>> I'm looking for an information regarding exception handling on Linux/m68k,
>> in particular
>> I need to know what registers are used by t
ontent.com/llvm/llvm-project/master/llvm/lib/Target/X86/X86ISelLowering.cpp
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
see if you can throw/catch exceptions between code
> compiled by your llvm port and a gcc
Perfect, thanks.
> hope that helps.
I'll give it a try.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
would you actually favor the inclusion of Michael's changes?
Having gcc allow to work with such code would actually allow us
to bootstrap ghc on m68k again which would be awesome :).
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `&
On 01/26/2016 11:07 AM, Andreas Schwab wrote:
> John Paul Adrian Glaubitz writes:
>
>> Having gcc allow to work with such code would actually allow us
>> to bootstrap ghc on m68k again which would be awesome :).
>
> The ghc code just needs to be fixed to not lie in su
this as crap code.
^
But I don't want to argue anyway. I was assuming ppc64le might have
similarities to m68k in that regard.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Univers
t;
> Like void, f.ex.
Wait. Do you think this would actually allow ghc to determine the
return type later? If I remember correctly, ghc currently initially
declares the function prototype with return type void*, doesn't it?
Adrian
--
.''`. John Paul Adrian Glaubitz
=sid
So gcc is tested regularly on ia64 and co and it's actively being used
to build the whole Debian archive.
Thanks,
Adrian
[1] https://gcc.gnu.org/ml/gcc/2019-06/msg00158.html
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `&
drian
> [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91851
> [2]
> https://www.bountysource.com/issues/80706251-m68k-convert-the-backend-to-mode_cc-so-it-can-be-kept-in-future-releases
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.o
it doesn't really work yet. I think finishing LLVM for m68k would be another
idea for a Bountysource campaign.
Adrian
> [1] https://github.com/M680x0/M680x0-llvm/
> [2] https://www.vutbr.cz/en/students/final-thesis?zp_id=34902
> [3] https://github.com/glaubitz/rust/tree/m68k-linux
--
https://buildd.debian.org/status/fetch.php?pkg=gcc-8&arch=powerpcspe&ver=8-20180402-1&stamp=1522856967&raw=0
Is there anything in the powerpcspe port that is currently making life for
the users or developers of other code harder?
Thanks,
Adrian
--
.''`. John Pa
ote: while referencing
'bcdacc'
184 | uByte bcdacc[(DIVOPLEN+1)*9+2]; /* for quotient in BCD, +1, +1 */
| ^~
make[2]: Leaving directory
'/home/glaubitz/gccrs/build/powerpc-unknown-linux-gnu/libgcc'
make[1]: *** [Makefile:13143: all-target-libgcc] Error
19 matches
Mail list logo
