public inbox for ecos-cvs@sourceware.org
help / color / mirror / Atom feed
From: jlarmour@sourceware.org
To: ecos-cvs@ecos.sourceware.org
Subject: ecos/packages/hal/common/current ChangeLog cdl ...
Date: Tue, 11 Nov 2008 04:28:00 -0000	[thread overview]
Message-ID: <20081111042857.19382.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/ecos
Module name:	ecos
Changes by:	jlarmour@sourceware.org	2008-11-11 04:28:57

Modified files:
	packages/hal/common/current: ChangeLog 
	packages/hal/common/current/cdl: common.cdl hal.cdl 
	packages/hal/common/current/include: hal_stub.h 
	packages/hal/common/current/src: generic-stub.c hal_if.c 
	                                 thread-packets.c 

Log message:
	* src/thread-packets.c (threadmatch): Silence pointer signedness
	warning.
	(threadref_to_int): Ditto.
	* src/generic-stub.c (__mem2hex): Ditto.
	(__mem2hex_safe): Ditto.
	(__hex2mem): Ditto.
	(__hex2mem_safe): Ditto.
	* src/hal_if.c (delay_us): Ditto.
	* include/hal_stub.h (CYG_HAL_GDB_LEAVE_CRITICAL_IO_REGION):
	Instead of using a local variable to avoid compiler reordering
	when taking the address of a label, instead call an external function.
	(NB making the variable volatile isn't sufficient).
	
	* cdl/hal.cdl: Work around problem with current ARM EABI tools by
	using /dev/null as linker script. Should be safe with other tools.
	
	* src/hal_if.c (delay_us): use HAL_DELAY_US() rather than the
	fancy implementation if the port cannot provide HAL_CLOCK_READ()
	
	* cdl/common.cdl: Add CYGBLD_HAL_LINKER_GROUPED_LIBS to allow
	CDL setting of libraries used for GROUP() directive in linker
	script.


             reply	other threads:[~2008-11-11  4:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11  4:28 jlarmour [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-11-20 20:42 jld
2004-02-23 14:55 jlarmour
2003-04-08  1:13 jlarmour
2003-02-24 14:22 jlarmour
2002-12-04  6:29 gthomas
2002-12-03 11:48 gthomas
2002-11-13 13:04 gthomas

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=20081111042857.19382.qmail@sourceware.org \
    --to=jlarmour@sourceware.org \
    --cc=ecos-cvs@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).