[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2024-03-03 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #65 from GCC Commits --- The master branch has been updated by Georg-Johann Lay : https://gcc.gnu.org/g:dae3456965064c9664c097c785ae9bf9fa203fa0 commit r14-9280-gdae3456965064c9664c097c785ae9bf9fa203fa0 Author: Georg-Johann Lay

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2023-06-10 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #64 from CVS Commits --- The releases/gcc-12 branch has been updated by Georg-Johann Lay : https://gcc.gnu.org/g:ee92dc2dae45acc79d4dc08ea31adf894831840a commit r12-9691-gee92dc2dae45acc79d4dc08ea31adf894831840a Author:

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2023-06-10 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #63 from CVS Commits --- The releases/gcc-13 branch has been updated by Georg-Johann Lay : https://gcc.gnu.org/g:6165b233ecc637efb5edcad8a34aae74b165a711 commit r13-7436-g6165b233ecc637efb5edcad8a34aae74b165a711 Author:

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2023-06-10 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #62 from CVS Commits --- The master branch has been updated by Georg-Johann Lay : https://gcc.gnu.org/g:30a8771c0f5ddcbc329408c3bbf4f100b01acca9 commit r14-1688-g30a8771c0f5ddcbc329408c3bbf4f100b01acca9 Author: Georg-Johann Lay

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-05-13 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #61 from abebeos at lazaridis dot com --- Now, the headline would be: "Physik FU-Berlin, Microchip, Google, RedHat, IBM and more to Support Abuse, Discrimination and even 'IT-fascism' via/on GCC/GNU/FSF Project-Resources". See,

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-05-12 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #60 from abebeos at lazaridis dot com --- Notable sub-message: https://gcc.gnu.org/pipermail/gcc-patches/2021-May/570039.html And the final essence, from: https://gcc.gnu.org/pipermail/gcc-patches/2021-May/570044.html " GCC issue,

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-05-09 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #59 from abebeos at lazaridis dot com --- Oh my, what a mess: https://gcc.gnu.org/pipermail/gcc-patches/2021-May/569913.html

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-05-07 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #58 from abebeos at lazaridis dot com --- Well, now I'm really really curious. Does the gcc project have at least some(!) liberal qualities, or will IT-fascism win? Follow-up: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100480

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-05-02 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #57 from abebeos at lazaridis dot com --- Just fascinating! Bountysource violated its own processes, and payed out the bounty without waiting for the votes. See, even without a dispute, there is a 2 week voting period ("The bounty

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-05-01 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #56 from abebeos at lazaridis dot com --- Oh, Mr. Glaubitz, thank you for your opinion. It is you very personal choice to ignore "integration work" and label "reuse of existent results" as "copy". I assume this does not reflect on

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-05-01 Thread glaubitz at physik dot fu-berlin.de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #55 from John Paul Adrian Glaubitz --- (In reply to abebeos from comment #54) > Now, there is a strange tendency within this project to completely ignore my > work on this issue/bounty and my person, see e.g. here: You have no claim

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-05-01 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #54 from abebeos at lazaridis dot com --- Bounty Claim: Please not that "saaadhu"s patch was "shelved". I integrated a validation-setup and tested several existent solutions, and identified during the "reuse existent work" phase of

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-05-01 Thread shiftee at posteo dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 Mark O'Donovan changed: What|Removed |Added CC||shiftee at posteo dot net --- Comment

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-04-30 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #52 from abebeos at lazaridis dot com --- All good, found it: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=3ba781d3b5c8efadb60866c9743b657e8f0eb222

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-04-30 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #51 from abebeos at lazaridis dot com --- @Senthil, can you please provide the links to the commits? I was unable to locate them.

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-04-30 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #50 from abebeos at lazaridis dot com --- Great! It looks that bountysource does not allow to split a bounty. Any suggestions on how to process this further?

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-04-30 Thread saaadhu at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 Senthil Kumar Selvaraj changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2021-02-06 Thread saaadhu at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #48 from Senthil Kumar Selvaraj --- Submitted https://gcc.gnu.org/pipermail/gcc-patches/2021-January/563638.html, which addresses comments made when the work-in-progress version was submitted. There are no regression failures (save

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-16 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #47 from abebeos at lazaridis dot com --- Relevant news: https://gcc.gnu.org/pipermail/gcc-patches/2020-December/562114.html

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-13 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #46 from abebeos at lazaridis dot com --- This addresses the Bounty-Backers: https://github.com/abebeos/avr-gnu/blob/master/doc/README.md

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-13 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #45 from abebeos at lazaridis dot com --- (In reply to abebeos from comment #40) > (In reply to John Paul Adrian Glaubitz from comment #39) [...] > I spend nearly a full-(over)-time month to achieve a result, fighting > through

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-13 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 abebeos at lazaridis dot com changed: What|Removed |Added CC||chertykov at gmail dot com

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-12 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #43 from abebeos at lazaridis dot com --- The patch is now (after further validation zero regressions within gcc/g++ testsuite in 2 different test-setups) "out there":

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-10 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #42 from abebeos at lazaridis dot com --- from Dimitar Dimitrov dimi...@dinux.eu within https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561489.html > I tested the trees you have given with my own AVR test setup [1]. I confirm

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-09 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #41 from abebeos at lazaridis dot com --- [RFC] [avr] Toolchain Integration for Testsuite Execution (avr cc0 to mode_cc0 conversion) https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561427.html

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-07 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #40 from abebeos at lazaridis dot com --- (In reply to John Paul Adrian Glaubitz from comment #39) > (In reply to abebeos from comment #38) > > Can someone please ping gcc-patches (me having troubles setting up email > > alias on

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-07 Thread glaubitz at physik dot fu-berlin.de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #39 from John Paul Adrian Glaubitz --- (In reply to abebeos from comment #38) > Can someone please ping gcc-patches (me having troubles setting up email > alias on gmail, don't want to use my main email) I'm not sure what you are

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-07 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #38 from abebeos at lazaridis dot com --- Can someone please ping gcc-patches (me having troubles setting up email alias on gmail, don't want to use my main email)

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-06 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #37 from abebeos at lazaridis dot com --- ?

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-04 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #36 from abebeos at lazaridis dot com --- Created attachment 49686 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49686=edit Patch by Senthil Kumar Selvaraj, non-cc0-avr-backend this should(!) be the final patch, derived from:

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-03 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #35 from abebeos at lazaridis dot com --- (In reply to abebeos from comment #11) > (In reply to John Paul Adrian Glaubitz from comment #10) > [...] > > The main problem is apparently that the target hasn't been properly worked > > on

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-02 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #34 from abebeos at lazaridis dot com --- (In reply to abebeos from comment #29) [...] > I will today focus on publishing my test-setup, so that my test-results can > be peer-reviewed. Should be available within 12 hours, max 36.

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-02 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #33 from abebeos at lazaridis dot com --- (In reply to John Paul Adrian Glaubitz from comment #31) [...] > The question will also be who will get to claim the bounty? If everyone > contributes something, it will be more difficult to

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-02 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #32 from abebeos at lazaridis dot com --- (In reply to Jonathan Wakely from comment #30) > (In reply to abebeos from comment #29) > > My understanding is that you have already contributor status here, so could > > you make the patch

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-02 Thread glaubitz at physik dot fu-berlin.de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #31 from John Paul Adrian Glaubitz --- (In reply to Jonathan Wakely from comment #30) > I don't think that's true, is it? I think Senthil Kumar needs to complete > the paperwork with the FSF for the patches to be "available to the

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-02 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #30 from Jonathan Wakely --- (In reply to abebeos from comment #29) > My understanding is that you have already contributor status here, so could > you make the patch available to the project? I don't think that's true, is it? I

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-02 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #29 from abebeos at lazaridis dot com --- (In reply to abebeos from comment #23) > (In reply to Senthil Kumar Selvaraj from comment #21) > > (https://github.com/saaadhu/gcc-avr-cc0/tree/avr-cc0-squashed) > > I can still do a

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-12-01 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #28 from abebeos at lazaridis dot com --- (In reply to Senthil Kumar Selvaraj from comment #21) [...] > I don't have the spare time now to start full fledged work on this, but I > can help with any issues you run into. Just a

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-30 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #27 from abebeos at lazaridis dot com --- The "contrib/compare_tests" created a wrong delta. "contrib/dg-cmp-results.sh seems to produce a more concise delta, and it shows that... ==> ...we are down to essentially 6 issues:

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-30 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #26 from abebeos at lazaridis dot com --- (In reply to Richard Biener from comment #24) > Amending / adjusting > https://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc > (the only place that somewhat "documents" how to setup AVR

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-30 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #25 from abebeos at lazaridis dot com --- (In reply to John Paul Adrian Glaubitz from comment #22) [...] > > https://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html FSF has a fascinating way to make trivial things

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-30 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #24 from Richard Biener --- Amending / adjusting https://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc (the only place that somewhat "documents" how to setup AVR testing) is appreciated.

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-30 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #23 from abebeos at lazaridis dot com --- (In reply to Senthil Kumar Selvaraj from comment #21) > (https://github.com/saaadhu/gcc-avr-cc0/tree/avr-cc0-squashed) I can still do a test-run, to see if it produces less fails than pip's

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-30 Thread glaubitz at physik dot fu-berlin.de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #22 from John Paul Adrian Glaubitz --- (In reply to abebeos from comment #20) > Testsuite comparison on local dev system looks quite good: > > https://github.com/abebeos/avr-gnu/issues/1 Just as a heads-up: Please keep in mind that

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-30 Thread saaadhu at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 Senthil Kumar Selvaraj changed: What|Removed |Added CC||saaadhu at gcc dot gnu.org ---

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-30 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #20 from abebeos at lazaridis dot com --- Testsuite comparison on local dev system looks quite good: https://github.com/abebeos/avr-gnu/issues/1

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-29 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #19 from abebeos at lazaridis dot com --- pipcet, thank you for your quick response (both here and within email). I think all here will agree that there's no need to apologize, as family/health should always come first. As for your

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-29 Thread pipcet at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #18 from pipcet at gmail dot com --- Sorry for only getting back to this now. I release all code on this branch into the public domain, if it helps at all. I'm happy to add whatever legal attribution is needed for that. I'm willing

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-28 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #17 from abebeos at lazaridis dot com --- Things look well, me being on 2 parallel solution paths: a) using https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729#c6 as a foundation. b) focusing more on a from-scratch work (cc0

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-18 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #16 from abebeos at lazaridis dot com --- I've updated the bounty, and you can follow the work here: https://github.com/abebeos/avr-gnu Whenever something relevant happens, I'll report it here.

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-15 Thread gjl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #15 from Georg-Johann Lay --- I built the tools by hand so I knew what I had... Dunno about gcc/buildbot policies concerning avr. As avr as a 3ary target, that BE's quality is of no consideration when releasing the compiler. Again,

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-15 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #14 from abebeos at lazaridis dot com --- (In reply to Georg-Johann Lay from comment #12) > [...]you'll have to resolve conflicts. (In reply to Georg-Johann Lay from comment #13) > FYI, avrtest is here: >

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-15 Thread gjl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #13 from Georg-Johann Lay --- FYI, avrtest is here: https://sourceforge.net/p/winavr/code/HEAD/tree/trunk/avrtest/

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-14 Thread gjl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #12 from Georg-Johann Lay --- Simulator: avrtest core simulator hosted on SourceForge as part of WinAVR. Libc: avr-libc trunk hosted on nongnu.org. There are several patches not yet integrated: recent xtiny devices, fixes in libm to

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-11 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #11 from abebeos at lazaridis dot com --- (In reply to John Paul Adrian Glaubitz from comment #10) [...] > The main problem is apparently that the target hasn't been properly worked > on for a long time. [...] Yes, this seems to

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-10 Thread glaubitz at physik dot fu-berlin.de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #10 from John Paul Adrian Glaubitz --- (In reply to abebeos from comment #9) > So, if it's ok for the backers, reduce the scope of the bounty to "just get > avr into gcc11 and keep generated code as much as possible unchanged". It

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-11-10 Thread abebeos at lazaridis dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 abebeos at lazaridis dot com changed: What|Removed |Added CC||abebeos at lazaridis dot

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-10-09 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #8 from Jonathan Wakely --- And please ping patches like https://gcc.gnu.org/pipermail/gcc-patches/2020-August/552844.html if you don't get a review.

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-08-06 Thread glaubitz at physik dot fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #7 from John Paul Adrian Glaubitz --- > I'd be really grateful for advice on how to test and improve this. Is there a > test suite somewhere that I've missed? Ideally, one that works with a free > simulator? Probably best to ask

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-08-04 Thread pipcet at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #6 from pipcet at gmail dot com --- I've just pushed here https://github.com/gcc-mirror/gcc/compare/master...pipcet:avr-ccmode-20200804?expand=1 the current state of my work as a series of git commits, sorted roughly from large,

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-07-29 Thread pipcet at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 pipcet at gmail dot com changed: What|Removed |Added CC||pipcet at gmail dot com ---

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-05-22 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #4 from Tobias Burnus --- See also https://gcc.gnu.org/pipermail/gcc/2020-April/thread.html#402 (for details/current status, ask those involved).

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-05-22 Thread glaubitz at physik dot fu-berlin.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #3 from John Paul Adrian Glaubitz --- (In reply to Max from comment #2) > Is there anyone more familiar with GCC internals and/or the AVR backend who > I would be able to consult or possibly work with on this? I think Jeff Law

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-05-21 Thread f.mach4 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 Max changed: What|Removed |Added CC||f.mach4 at gmail dot com --- Comment #2 from Max

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-02-24 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment

[Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases

2020-01-30 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|2019-11-30