On Jun 23, 2016, at 5:21 AM, Senthil Kumar Selvaraj
wrote:
>
> 2. Even if (1) is fixed, the custom section (.foo) is not mapped to
> any output section or region in the linker script. The linker can
> error out only if the contents overflow a region.
If the segment isn't loaded, then it's size
On Jun 23, 2016, at 4:00 AM, Georg-Johann Lay wrote:
> Binutils don't produce a message
That's unfortunate.
> so there is nothing to scan for. Hacking binutils is beyond my scope.
That's fine.
> avrtest behaves just as if the program under test would call abort.
That's unfortunate. Would be
Georg-Johann Lay writes:
> On 22.06.2016 19:06, Mike Stump wrote:
>> On Jun 22, 2016, at 7:21 AM, Georg-Johann Lay wrote:
>>>
>>> Some tests for PR71151 assume that the target MCU has a 3-byte PC. The
>>> tests are failing because the simulator (avrtest) rejects to load the
>>> respective execut
On 22.06.2016 19:06, Mike Stump wrote:
On Jun 22, 2016, at 7:21 AM, Georg-Johann Lay wrote:
Some tests for PR71151 assume that the target MCU has a 3-byte PC. The
tests are failing because the simulator (avrtest) rejects to load the
respective executables if .text exceeds 128KiB, e.g. for -mmc
