summaryrefslogtreecommitdiffstats
path: root/c/src/exec/score (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Modified _Objects_Is_class_valid() to correctly report that 0 wasJoel Sherrill1998-06-184-4/+4
| | | | | not a valid object class. This was discovered while looking for a bug reported by Jennifer.
* Added freebsd support from Dario Alcocer <alcocer@connectnet.com>.Joel Sherrill1998-06-184-2/+27
|
* Added optimized version of memcpy.c to this directory since RTEMS makesJoel Sherrill1998-06-122-1/+88
| | | | | | important distinctions between CPU models which are not made by gcc. These distinctions help give us a more optimized memcpy(). This is important for message queues and KA9Q.
* Added CPU_ISR_PASSES_FRAME_POINTER so some ports could pass just theJoel Sherrill1998-06-0313-0/+133
| | | | | vector number to user ISR's and other ports could pass both the vector number and a pointer to the ISF.
* Corrected macros for assembly language program sections.Joel Sherrill1998-06-031-2/+2
|
* Fixed spacingJoel Sherrill1998-05-271-16/+16
|
* Fix from Jiri Gaisler <jgais@ws.estec.esa.nl> for a problem in whichJoel Sherrill1998-05-271-1/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | external interrupt priorities were not being honored. Here is some of his original report: using rtems/erc32, I have a problem with interrupt priority when interrupts occure simultaneously. Erc32 has an interrupt force register where interrupts can be generated. If more than one interrupt is generated, the interrupt handlers are scheduled in the wrong order, i.e. with the lowest priority first. I have attched a program that generates three interrupts, 0x11, 0x12 and 0x13. Interrupt 0x13 should be handled first, but is actually handled last. Below is the output from sis: sis> go resuming at 0x02000000 RAM size: 4096 K, ROM size: 2048 K Watchdog disabled Waitstates = RAM read: 0, RAM write: 0, ROM read: 0, ROM write: 0 Power-down mode enabled infinite UART baudrate External interrupt received with vector 0x11 External interrupt received with vector 0x12 External interrupt received with vector 0x13 I have verified that sis generates the interrupts in the correct order, i.e. 0x13 first, then 0x12 and then 0x11. So the problem seems to be in the rtems interrupt handler. Do you use the PIL field in the %psr register to mask lower priority interrupts or are all external interrupts considered to have the same priority ..? Here is a description of the fix: it turned out that lower priority interrupts were not at all masked off during interrupt handling. I made the following fix to cpu_asm.s: ... fix is in the code ... There might be a simpler way of doing this, but this works...
* Per suggestion from Ralf Corsepius made all macros solaris2 -- not solarisJoel Sherrill1998-05-211-1/+1
| | | | or solaris2.
* Added bsp_specs.Joel Sherrill1998-05-181-3/+4
|
* fixed swap of unsigned16Joel Sherrill1998-05-041-6/+6
|
* Fixed case where wrong variable was used.Joel Sherrill1998-04-301-1/+1
|
* Added I386_HAS_BSWAP cpu model feature flag so swap u32 could takeJoel Sherrill1998-04-271-10/+28
| | | | | | | | advantage of this instruction. Also up conditionals mapping cpu models to feature flags by having a section which defaults all the i386 family feature flags to the most common value.
* Added swap of unsigned16Joel Sherrill1998-04-2711-3/+69
|
* Fixed spelling errors.Joel Sherrill1998-04-271-3/+3
|
* Fixed trace bit manipulation per requests from Eric Norum and Chris Johns.Joel Sherrill1998-04-271-11/+3
| | | | Actual patch was from Eric Norum.
* Fixed CVS IdJoel Sherrill1998-04-271-1/+1
|
* Added bh, ch, dh, bl, cl, and dl register macros.Joel Sherrill1998-04-151-0/+7
|
* Per suggestion from Eric Norum, went from one initial extension setJoel Sherrill1998-04-154-18/+26
| | | | | | to multiple. This lets the stack check extension be installed at system initialization time and avoids the BSP having to even know about its existence.
* Ralf Corsepius suggested a way to get rid of UNIX compiler files and use ↵Joel Sherrill1998-04-142-2/+1
| | | | gcc-target-default.cfg
* Refreshing effort from Avenger.Joel Sherrill1998-04-148-322/+1046
|
* Added "sigemptyset()" call to insure that the memcmp() would work.Joel Sherrill1998-03-311-0/+4
| | | | | It appears that the new glibc does not clear all the bits of the signal set with a sigprocmask.
* Changed int to unsigned32 to match cpu.h.Joel Sherrill1998-03-271-1/+1
|
* m68k software interrupt stack support from Chris Johns and Eric Norum.Joel Sherrill1998-03-253-32/+36
|
* Added _XOPEN_SOURCE definition to allow use of UNIX IPC.Joel Sherrill1998-03-241-0/+1
|
* Real definition for the beginning of the data section per Eric Norum'sJoel Sherrill1998-03-241-2/+2
| | | | suggestion.
* Corrected register constraints per suggestion from Thomas Doerfler, IMDJoel Sherrill1998-03-242-6/+6
| | | | <td@imd.m.isar.de>.
* More cpu model flags converted to using cpp predefines.Joel Sherrill1998-03-241-2/+2
|
* Rename hppa1_1 to hppa1.1 and switched to using __XXX__ macros forJoel Sherrill1998-03-242-14/+14
| | | | the CPU family name constants.
* Renamed hppa1_1 to hppa1.1Joel Sherrill1998-03-231-4/+1
|
* renamed ppc to powerpcJoel Sherrill1998-03-231-1/+0
|
* Fixed spacing to be consistent with other CPUs.Joel Sherrill1998-03-211-1/+1
|
* Patch from Eric Norum <eric@skatter.usask.ca>:Joel Sherrill1998-03-201-81/+75
| | | | | | Here is my attempt at bringing m68k.h into line with the predefined symbols provided by egcs-1.0.2-prerelease (with R. Kirkham's patch so that -mcpu32, etc. implies -msoft-float).
* SH port submitted from Ralf Corsepius <corsepiu@faw.uni-ulm.de>.Joel Sherrill1998-03-2013-0/+2869
|
* Removed use of dc. David Fiddes reported that this is part of theJoel Sherrill1998-02-271-1/+17
| | | | | GNU tool bc which is not always installed under Linux and seldom present under non-UNIX environments like Win32.
* Modified to make it possible for an ISR to return a mutex which didJoel Sherrill1998-02-201-2/+20
| | | | not use priority ceiling or priority inheritance protocols.
* Ralf Corsepius noted that there was a dead path in _Thread_Initialize.Joel Sherrill1998-02-181-6/+2
|
* updated copyright to 1998Joel Sherrill1998-02-17225-229/+229
|
* Renamed init.o to exinit.o to avoid naming conflicts with tests.Joel Sherrill1998-02-171-2/+2
|
* Swapped C++ and ASM "endifs"Joel Sherrill1998-02-171-2/+2
|
* Fixed to correctly operate on target variants like debug and profile.Joel Sherrill1998-02-071-9/+23
|
* Ralf Corsepius noticed that generally was spelled incorrectly.Joel Sherrill1998-02-0411-11/+11
|
* Big patch form Ralf Corsepius described in this email:Joel Sherrill1998-01-3023-92/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Here is the result of my nightly work to get RTEMS_ROOT=$srcdir working with different shells and relative/absolute paths. What I did is relatively simple in principle: Instead of setting RTEMS_ROOT in configure.in and then let configure substitute @RTEMS_ROOT@ inside the Makefiles, I now let each Makefile set RTEMS_ROOT from each Makefile's @top_srcdir@ value. The difference is subtile, but with enormous side effects: - If RTEMS_ROOT is set in configure, then the same single value will be propagated to all Makefiles. This breaks using relative paths, as the relative path to the root of the source tree is used inside of all subdirectory Makefiles. - Now each Makefile.in sets RTEMS_ROOT = @top_srcdir@. top_srcdir is computed individually by configure for each single Makefile.in, hereby receiving the correct value, no matter if relative or absolute paths are used. To get this working, I needed to remove setting RTEMS_ROOT from target.cfg.in, because this overrides the value of RTEMS_ROOT from each individual Makefile. Furthermore, I removed RTEMS_CUSTOM from the Makefiles and replaced all "include $(RTEMS_CUSTOM)" directives with"include $(RTEMS_ROOT)/make/custom/$(RTEMS_BSP)". Perhaps you don't like this, but I think, to have one variable less is clearer and easier to understand than having several variables refering to the next one. I enclose a small patch to this mail, which - fixes the config.h problem (to finally clearify misunderstands) - removes assignment/subsitution of RTEMS_ROOT from configure.in - contains a workaround for the application Makefile's RTEMS_ROOT problem (reported by Eric) - removes some unused lines from the toplevel Makefile.in - removes assignment of RTEMS_ROOT from make/target.cfg.in
* Change to remove warning on glibc2 systems per Ralf Corsepius'sJoel Sherrill1998-01-281-1/+6
| | | | suggestion.
* Solaris port updates from Chris JohnsJoel Sherrill1998-01-231-10/+0
|
* Cleaned up a bit.Joel Sherrill1998-01-231-9/+31
|
* Removed warning per Chris Johns' suggestion.Joel Sherrill1998-01-204-4/+4
|
* Removed warning per Chris John's suggestion.Joel Sherrill1998-01-201-1/+1
|
* Removed CONFIG_DIR and PROJECT_HOME directories.Joel Sherrill1998-01-2023-23/+23
|
* Error reported by Duncan Smith <dds@flavors.com>:Joel Sherrill1998-01-152-2/+2
| | | | | | | | | | | | | | | | | | | | | | >> >>There is a 30 day error in _TOD_Days_since_last_leap_year[2..3] >> > >> >Thanks. >> >What's the condition to hit this error? >> >Every year 4n+2 and 4n+3 ? >> >(i.e. 1998, 1999, 2002, 2003, ...) >> > >> OK: 96 97 00 01 04 05 ... >> Bad: 98 99 02 03 06 07 ... There is also a problem in newlib 1.7.x reported at the same time: >> I found another, that would strike only on 2/29/2000, or other leapyears. >> Only a problem on 1 day. >> >> Joel: FYI, there is a bug in Newlib localtime.c, localtime or (_tm_time). >> Ours is modified for dst and timezones, but the bug was in original source. >> I have not looked at the latest public source (nor do I know where to find >> it).
* Fixed spacing.Joel Sherrill1998-01-061-2/+2
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-02 23:54:06 +0000