public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] OT: HiTech-C question
Date: Mon, 15 Nov 2010 15:53:21 +0100	[thread overview]
Message-ID: <20101115145321.6926.qmail@stuge.se> (raw)
In-Reply-To: <20101115073713.475b4adf@osage.osagesoftware.com> <4CE126AE.2@gmail.com>

Arkadi Shishlov wrote:
> Isn't the arrival of really cheap ARM-s, like M0, puts PIC and AVR
> and the like in legacy category you won't ever look again?

Yes and no. For the very smallest jobs, I think the cheapest PIC
still will beat an ARM by a bit. The PICs are also much smaller,
physically.

But I tend to agree. Used PIC since 90s, since starting with ARM
don't really think that I will look back.

> not to deal with PIC brain-damaging architecture is so relieving.

Hahaha! :) I kindof like it. The skip instructions are funny.


> People say, PIC-s are very robust and can handle a lot with theirs
> bare pin-s, but still, does it really matter most of the times?

Also a good point, the pins can sure take a beating.


David Relson wrote:
> At least one of HiTech's C compilers is gcc based.  Their 32-bit
> compiler documentation is a revised version of the gcc documentation.
> If recollection serves I think I saw a copy of the GPL, though I
> can't locate it right now.

Yes, they started out using their own fork of GCC for PIC32 (as
opposed to contributing support back into GCC) and since GCC is GPL
they are forced to publish their sources, which they also have done.
There was some community effort to clean it up and get it into GCC
proper, I don't know the status of that.

The C library is another story however. The C library that Microchip
released for their PIC32 to the public at no cost artificially limits
how large the application code can be. If you need larger you have to
buy the full version. They can do this because the C library is
separate from the compiler.


> James, I'd appreciate your posting your PIC open source references.

Here are some to get you started:

http://gputils.sf.net/ # assembler and linker
http://sdcc.sf.net/    # C compiler
http://gpsim.sf.net/   # simulator
http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/1  # mailing list
http://pikdev.free.fr/ # a GUI IDE

The list is rather low volume, but has been around since 99. I would
suggest to post there any and all questions, and I believe you will
get good answers.


//Peter



  parent reply	other threads:[~2010-11-15 15:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15  2:10 [gentoo-embedded] OT: HiTech-C question David Relson
2010-11-15  3:37 ` Peter Stuge
2010-11-15  7:44   ` Mike Frysinger
2010-11-15 11:22 ` wireless
2010-11-15 12:25   ` Arkadi Shishlov
2010-11-15 14:45     ` wireless
2010-11-15 16:05       ` Peter Stuge
2010-11-15 18:13         ` wireless
2010-11-15 18:53           ` Peter Stuge
2010-11-15 19:28           ` Arkadi Shishlov
2010-11-15 14:53     ` Peter Stuge [this message]
2010-11-15 12:37   ` David Relson
2010-11-15 14:25     ` wireless

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101115145321.6926.qmail@stuge.se \
    --to=peter@stuge.se \
    --cc=gentoo-embedded@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox