Re: Optimization issue in RISC-V BSP

On Jul 28, 2017 7:11 PM, "Denis Obrezkov" wrote: 2017-07-29 1:41 GMT+02:00 Joel Sherrill : > > > On Jul 28, 2017 6:39 PM, "Denis Obrezkov" wrote: > > 2017-07-29 1:28 GMT+02:00 Joel Sherrill : > >> >> >> On Jul 28, 2017 6:14 PM, "Denis Obrezkov" >> wrote: >> >> 2017-07-29 0:57 GMT+02:00 Joel Sh

Re: Optimization issue in RISC-V BSP

2017-07-29 1:41 GMT+02:00 Joel Sherrill : > > > On Jul 28, 2017 6:39 PM, "Denis Obrezkov" wrote: > > 2017-07-29 1:28 GMT+02:00 Joel Sherrill : > >> >> >> On Jul 28, 2017 6:14 PM, "Denis Obrezkov" >> wrote: >> >> 2017-07-29 0:57 GMT+02:00 Joel Sherrill : >> >>> >>> >>> On Jul 28, 2017 5:55 PM, "D

Re: Optimization issue in RISC-V BSP

On Jul 28, 2017 6:39 PM, "Denis Obrezkov" wrote: 2017-07-29 1:28 GMT+02:00 Joel Sherrill : > > > On Jul 28, 2017 6:14 PM, "Denis Obrezkov" wrote: > > 2017-07-29 0:57 GMT+02:00 Joel Sherrill : > >> >> >> On Jul 28, 2017 5:55 PM, "Denis Obrezkov" >> wrote: >> >> 2017-07-28 22:36 GMT+02:00 Joel S

Re: Optimization issue in RISC-V BSP

2017-07-29 1:28 GMT+02:00 Joel Sherrill : > > > On Jul 28, 2017 6:14 PM, "Denis Obrezkov" wrote: > > 2017-07-29 0:57 GMT+02:00 Joel Sherrill : > >> >> >> On Jul 28, 2017 5:55 PM, "Denis Obrezkov" >> wrote: >> >> 2017-07-28 22:36 GMT+02:00 Joel Sherrill : >> >>> Can you check the memory immediate

Re: Optimization issue in RISC-V BSP

On Jul 28, 2017 6:14 PM, "Denis Obrezkov" wrote: 2017-07-29 0:57 GMT+02:00 Joel Sherrill : > > > On Jul 28, 2017 5:55 PM, "Denis Obrezkov" wrote: > > 2017-07-28 22:36 GMT+02:00 Joel Sherrill : > >> Can you check the memory immediately after a download'? >> >> Then after the loop that copies ini

Re: Optimization issue in RISC-V BSP

2017-07-29 0:57 GMT+02:00 Joel Sherrill : > > > On Jul 28, 2017 5:55 PM, "Denis Obrezkov" wrote: > > 2017-07-28 22:36 GMT+02:00 Joel Sherrill : > >> Can you check the memory immediately after a download'? >> >> Then after the loop that copies initialized data into place? >> >> I suspect something

Re: Optimization issue in RISC-V BSP

On Jul 28, 2017 5:55 PM, "Denis Obrezkov" wrote: 2017-07-28 22:36 GMT+02:00 Joel Sherrill : > Can you check the memory immediately after a download'? > > Then after the loop that copies initialized data into place? > > I suspect something off there. Could be a linker script issue or the > copy g

Re: Optimization issue in RISC-V BSP

2017-07-28 22:36 GMT+02:00 Joel Sherrill : > Can you check the memory immediately after a download'? > > Then after the loop that copies initialized data into place? > > I suspect something off there. Could be a linker script issue or the > copy gone crazy. > > --joel > > On Fri, Jul 28, 2017 at 3

Re: Optimization issue in RISC-V BSP

Can you check the memory immediately after a download'? Then after the loop that copies initialized data into place? I suspect something off there. Could be a linker script issue or the copy gone crazy. --joel On Fri, Jul 28, 2017 at 3:20 PM, Denis Obrezkov wrote: > 2017-07-28 22:16 GMT+02:00

Re: Optimization issue in RISC-V BSP

2017-07-28 22:16 GMT+02:00 Joel Sherrill : > > > On Fri, Jul 28, 2017 at 2:50 PM, Denis Obrezkov > wrote: > >> I can see that during task initialization I have a call: _Thread_Initialize_information (information=information@entry=0x8ad4 <_RTEMS_tasks_Information>, the_api=the_

Re: Optimization issue in RISC-V BSP

On Fri, Jul 28, 2017 at 2:50 PM, Denis Obrezkov wrote: > >>> I can see that during task initialization I have a call: >>> _Thread_Initialize_information (information=information@entry=0x8ad4 >>> <_RTEMS_tasks_Information>, the_api=the_api@entry=OBJECTS_CLASSIC_API, >>> the_class=the_class@en

Re: Optimization issue in RISC-V BSP

> > >> I can see that during task initialization I have a call: >> _Thread_Initialize_information (information=information@entry=0x8ad4 >> <_RTEMS_tasks_Information>, the_api=the_api@entry=OBJECTS_CLASSIC_API, >> the_class=the_class@entry=1, maximum=124, >> is_string=is_string@entry=false,

Help Request Fixing Raspberry Pi Warnings

Hi Help would be appreciated in eliminating these two warnings: log/arm-raspberrypi.log:../../../../../../../../rtems/c/src/lib/libbsp/arm/raspberrypi/irq/irq.c:123:16: warning: implicit declaration of function 'ffs' [-Wimplicit-function-declaration] log/arm-raspberrypi.log:../../../../../../../.

Re: Optimization issue in RISC-V BSP

On Fri, Jul 28, 2017 at 10:31 AM, Denis Obrezkov wrote: > 2017-07-28 17:05 GMT+02:00 Joel Sherrill : > >> >> >> On Fri, Jul 28, 2017 at 9:23 AM, Denis Obrezkov >> wrote: >> >>> 2017-07-28 15:19 GMT+02:00 Sebastian Huber < >>> sebastian.hu...@embedded-brains.de>: >>> On 28/07/17 15:15, Denis

Re: Optimization issue in RISC-V BSP

2017-07-28 17:31 GMT+02:00 Denis Obrezkov : > 2017-07-28 17:05 GMT+02:00 Joel Sherrill : > >> >> >> On Fri, Jul 28, 2017 at 9:23 AM, Denis Obrezkov >> wrote: >> >>> 2017-07-28 15:19 GMT+02:00 Sebastian Huber < >>> sebastian.hu...@embedded-brains.de>: >>> On 28/07/17 15:15, Denis Obrezkov wro

Re: Optimization issue in RISC-V BSP

On Fri, Jul 28, 2017 at 11:05 AM, Joel Sherrill wrote: > > > On Fri, Jul 28, 2017 at 9:23 AM, Denis Obrezkov > wrote: >> >> 2017-07-28 15:19 GMT+02:00 Sebastian Huber >> : >>> >>> On 28/07/17 15:15, Denis Obrezkov wrote: >>> 2017-07-28 14:56 GMT+02:00 Joel Sherrill >>>

Re: Optimization issue in RISC-V BSP

2017-07-28 17:05 GMT+02:00 Joel Sherrill : > > > On Fri, Jul 28, 2017 at 9:23 AM, Denis Obrezkov > wrote: > >> 2017-07-28 15:19 GMT+02:00 Sebastian Huber > ns.de>: >> >>> On 28/07/17 15:15, Denis Obrezkov wrote: >>> >>> 2017-07-28 14:56 GMT+02:00 Joel Sherrill >>> j...@rtems.org>>:

Re: Optimization issue in RISC-V BSP

On Fri, Jul 28, 2017 at 9:23 AM, Denis Obrezkov wrote: > 2017-07-28 15:19 GMT+02:00 Sebastian Huber brains.de>: > >> On 28/07/17 15:15, Denis Obrezkov wrote: >> >> 2017-07-28 14:56 GMT+02:00 Joel Sherrill >> j...@rtems.org>>: >>> >>> There is a debug option near the bottom of confdefs.h whic

Re: Optimization issue in RISC-V BSP

2017-07-28 15:19 GMT+02:00 Sebastian Huber < sebastian.hu...@embedded-brains.de>: > On 28/07/17 15:15, Denis Obrezkov wrote: > > 2017-07-28 14:56 GMT+02:00 Joel Sherrill > j...@rtems.org>>: >> >> There is a debug option near the bottom of confdefs.h which you >> can enable to generate a da

Fwd: [rtems commit] psxtests/psxmmap01: Fix warning

This is printing a pointer and should have been a %p not adding a cast. -- Forwarded message -- From: Sebastian Huber Date: Fri, Jul 28, 2017 at 6:54 AM Subject: [rtems commit] psxtests/psxmmap01: Fix warning To: v...@rtems.org Module:rtems Branch:master Commit:77cbb

Re: Optimization issue in RISC-V BSP

On Fri, Jul 28, 2017 at 8:19 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 28/07/17 15:15, Denis Obrezkov wrote: > > 2017-07-28 14:56 GMT+02:00 Joel Sherrill > j...@rtems.org>>: >> >> There is a debug option near the bottom of confdefs.h which you >> can enable to g

Re: Optimization issue in RISC-V BSP

On 28/07/17 15:15, Denis Obrezkov wrote: 2017-07-28 14:56 GMT+02:00 Joel Sherrill >: There is a debug option near the bottom of confdefs.h which you can enable to generate a data structure filled in with various values computed by confdefs. You can look at tha

Re: Optimization issue in RISC-V BSP

2017-07-28 14:56 GMT+02:00 Joel Sherrill : > There is a debug option near the bottom of confdefs.h which you can enable > to generate a data structure filled in with various values computed by > confdefs. You can look at that in gdb without loading it on the target. > > It is probably worth it to

Re: Optimization issue in RISC-V BSP

2017-07-28 13:11 GMT+02:00 Gedare Bloom : > On Thu, Jul 27, 2017 at 7:43 PM, Denis Obrezkov > wrote: > > I didn't want to enable optimization because I was afraid of new > mistakes. > > So, I enabled -Os and now I have: > > _Terminate (the_source=the_source@entry=INTERNAL_ERROR_CORE, > > the_erro

Re: Optimization issue in RISC-V BSP

On Thu, Jul 27, 2017 at 7:43 PM, Denis Obrezkov wrote: > I didn't want to enable optimization because I was afraid of new mistakes. > So, I enabled -Os and now I have: > _Terminate (the_source=the_source@entry=INTERNAL_ERROR_CORE, > the_error=the_error@entry=3) > at > /home/reprofy/Projects/ri

[PATCH] score: Add RTEMS_HAVE_MEMBER_SAME_TYPE()

This fixes some "variably modified" warnings and a clang compile error. --- cpukit/score/include/rtems/score/basedefs.h| 19 +++ cpukit/score/include/rtems/score/threadqimpl.h | 8 ++-- 2 files changed, 25 insertions(+), 2 deletions(-) diff --git a/cpukit/score/include/rt

Re: Release candidate tool chain for 4.12

On 27 July 2017 at 23:28, Chris Johns wrote: > On 28/07/2017 00:40, Joel Sherrill wrote: >> On Thu, Jul 27, 2017 at 7:50 AM, Sebastian Huber >> > > >> wrote: >> >> Hallo, >> >> the GCC 7.2 release will be probably in two weeks. I would like to use