On 13/04/15 11:08, Martin Peres wrote:
On 02/04/15 13:27, Tapani Pälli wrote:
On 04/02/2015 12:36 PM, Martin Peres wrote:
On 01/04/15 15:14, Tapani Pälli wrote:
Previously linker did not take in to account case where one would
have only gs and fs (with SSO), patch adds the case by
On 02/04/15 13:27, Tapani Pälli wrote:
On 04/02/2015 12:36 PM, Martin Peres wrote:
On 01/04/15 15:14, Tapani Pälli wrote:
Previously linker did not take in to account case where one would
have only gs and fs (with SSO), patch adds the case by refactoring
code around
On 04/13/2015 11:18 AM, Martin Peres wrote:
On 13/04/15 11:08, Martin Peres wrote:
On 02/04/15 13:27, Tapani Pälli wrote:
On 04/02/2015 12:36 PM, Martin Peres wrote:
On 01/04/15 15:14, Tapani Pälli wrote:
Previously linker did not take in to account case where one would
have only gs
On 13/04/15 14:15, Tapani Pälli wrote:
On 04/13/2015 11:18 AM, Martin Peres wrote:
On 13/04/15 11:08, Martin Peres wrote:
On 02/04/15 13:27, Tapani Pälli wrote:
On 04/02/2015 12:36 PM, Martin Peres wrote:
On 01/04/15 15:14, Tapani Pälli wrote:
Previously linker did not take in to
On 01/04/15 15:14, Tapani Pälli wrote:
Previously linker did not take in to account case where one would
have only gs and fs (with SSO), patch adds the case by refactoring
code around assign_varying_locations. This makes sure locations for
gs get populated correctly.
This was found with some
On 04/02/2015 12:36 PM, Martin Peres wrote:
On 01/04/15 15:14, Tapani Pälli wrote:
Previously linker did not take in to account case where one would
have only gs and fs (with SSO), patch adds the case by refactoring
code around assign_varying_locations. This makes sure locations for
gs get
Previously linker did not take in to account case where one would
have only gs and fs (with SSO), patch adds the case by refactoring
code around assign_varying_locations. This makes sure locations for
gs get populated correctly.
This was found with some of the SSO subtests of Martin's upcoming
