GCC6809

The GCC maintainers have officially released version 4.3.4. This is a minor update, but it has been the basis of many new 6809 changes. Soon I'll be releasing a new 6809 package -- stay tuned.

The GCC maintainers have officially released version 4.3.4. This a minor update, but it has been the basis of many new 6809 changes. S...

It's perhaps not very clear where things are with the compiler now, so let me give a brief update. In particular I want to explain how I've been operating. A little more than a year ago, I switched over to Git for source control. GCC uses ... [More] Subversion as their VCS, but there is a Git repo that can be used for read-only access. I watch the 4.3, 4.4, and trunk branches from upstream. I have my own branches off each of this, where I made 6809-related changes. GCC 4.3 has been the most stable version of the compiler for me. Therefore, it is where I make all of my day-to-day feature changes. Initially, I was doing this in trunk and backporting everything, but this wasn't as easy. Granted, 4.3 is supposed to be a stable branch to the *upstream* developers, but for me it is a basis for ongoing development. I track 4.4 and 4.5 mainly out of curiosity to see that things still work. There have been problems with these (a topic for later) to where I don't really dwell on them too much, and I certainly don't encourage their use by others yet. So my 4.3 branch sees a lot of activity by me, plus it sees the occasional backporting from upstream of extremely stable bug fixes. At some point, the GCC developers will tag this with a new version number: the next would be GCC 4.3.4. At that point, I will put out a release such as gcc6809-4.3.4-1, with the last digit incremented if I make subsequent releases for some reason. I made end up changing this somewhat, because I realize there's a need for a stable and unstable version of the 6809 code itself, both based on GCC 4.3. Haven't figured out when or how to do this exactly, but it seems likely, especially once upstream locks down the GCC 4.3 branch forever. [Less]

It's perhaps not very clear where things are with the compiler now, so let me give a brief update. In particular I want to explain I'...

It's perhaps not very clear where things are with the compiler now, so let me give a brief update. In particular I want to explain how I've been operating. A little more than a year ago, I switched over to Git for source control. GCC uses ... [More] Subversion as their VCS, but there is a Git repo that can be used for read-only access. I watch the 4.3, 4.4, and trunk branches from upstream. I have my own branches off each of this, where I made 6809-related changes. GCC 4.3 has been the most stable version of the compiler for me. Therefore, it is where I make all of my day-to-day feature changes. Initially, I was doing this in trunk and backporting everything, but this wasn't as easy. Granted, 4.3 is supposed to be a stable branch to the *upstream* developers, but for me it is a basis for ongoing development. I track 4.4 and 4.5 mainly out of curiosity to see that things still work. There have been problems with these (a topic for later) to where I don't really dwell on them too much, and I certainly don't encourage their use by others yet. So my 4.3 branch sees a lot of activity by me, plus it sees the occasional backporting from upstream of extremely stable bug fixes. At some point, the GCC developers will tag this with a new version number: the next would be GCC 4.3.4. At that point, I will put out a release such as gcc6809-4.3.4-1, with the last digit incremented if I make subsequent releases for some reason. I made end up changing this somewhat, because I realize there's a need for a stable and unstable version of the 6809 code itself, both based on GCC 4.3. Haven't figured out when or how to do this exactly, but it seems likely, especially once upstream locks down the GCC 4.3 branch forever. [Less]

It's perhaps not very clear where things are with the compiler now, so let me give a brief update. In particular I want to explain how I've been operating. A little more than a year ago, I switched over to Git for source control. GCC uses ... [More] Subversion as their VCS, but there is a Git repo that can be used for read-only access. I watch the 4.3, 4.4, and trunk branches from upstream. I have my own branches off each of this, where I made 6809-related changes. GCC 4.3 has been the most stable version of the compiler for me. Therefore, it is where I make all of my day-to-day feature changes. Initially, I was doing this in trunk and backporting everything, but this wasn't as easy. Granted, 4.3 is supposed to be a stable branch to the *upstream* developers, but for me it is a basis for ongoing development. I track 4.4 and 4.5 mainly out of curiosity to see that things still work. There have been problems with these (a topic for later) to where I don't really dwell on them too much, and I certainly don't encourage their use by others yet. So my 4.3 branch sees a lot of activity by me, plus it sees the occasional backporting from upstream of extremely stable bug fixes. At some point, the GCC developers will tag this with a new version number: the next would be GCC 4.3.4. At that point, I will put out a release such as gcc6809-4.3.4-1, with the last digit incremented if I make subsequent releases for some reason. I made end up changing this somewhat, because I realize there's a need for a stable and unstable version of the 6809 code itself, both based on GCC 4.3. Haven't figured out when or how to do this exactly, but it seems likely, especially once upstream locks down the GCC 4.3 branch forever. [Less]

This is the first in what will hopefully be an informative series of postings regarding my port of GCC to the 6809 processor. In the past, I've posted updates to the website, but for those wanting to follow along at home, it's been difficult knowing ... [More] when something has changed -- and months often go by between updates. So hopefully, this feed will provide the information in an easier way. I considered a forum where people could post comments, but (1) that would take some additional work, and (2) the number of interested people is low enough that I don't really see the need for that. However, if you ARE interested and have something to say, by all means email me and I'll do my best to help. Coming soon, more information about where we are and what's to come ... [Less]

This is the first in what will hopefully be an informative series of postings regarding my port of GCC to the 6809 processor. In the past, ...

This is the first in what will hopefully be an informative series of postings regarding my port of GCC to the 6809 processor. In the past, I've posted updates to the website, but for those wanting to follow along at home, it's been difficult knowing ... [More] when something has changed -- and months often go by between updates. So hopefully, this feed will provide the information in an easier way. I considered a forum where people could post comments, but (1) that would take some additional work, and (2) the number of interested people is low enough that I don't really see the need for that. However, if you ARE interested and have something to say, by all means email me and I'll do my best to help. Coming soon, more information about where we are and what's to come ... [Less]