On Sat, Nov 14, 2020 at 8:21 PM David Michael wrote:
> On Sat, Nov 14, 2020 at 6:57 PM Carl Eugen Hoyos wrote:
> > Am Sa., 14. Nov. 2020 um 20:16 Uhr schrieb David Michael
> > :
> > > On Sat, Nov 14, 2020 at 2:06 PM Carl Eugen Hoyos
> > > wrote:
> >
On Sat, Nov 14, 2020 at 6:57 PM Carl Eugen Hoyos wrote:
> Am Sa., 14. Nov. 2020 um 20:16 Uhr schrieb David Michael
> :
> > On Sat, Nov 14, 2020 at 2:06 PM Carl Eugen Hoyos wrote:
> > > Am Sa., 14. Nov. 2020 um 18:22 Uhr schrieb David Michael
> > > :
> &
On Sat, Nov 14, 2020 at 2:06 PM Carl Eugen Hoyos wrote:
> Am Sa., 14. Nov. 2020 um 18:22 Uhr schrieb David Michael
> :
> >
> > There are two issues:
> >
> > When build systems enable LTO in CFLAGS, the unused global integer
> > does not make it into the co
, so the expected value will not
be matched when its four bytes are split across two lines. Use the
POSIX "-A n" option to disable printing input offsets and delete
all newline characters to output continuous hex values to grep.
Signed-off-by: David Michael
---
configure | 5 +++--
1 fi
On Thu, Nov 12, 2020 at 2:56 AM Carl Eugen Hoyos wrote:
> > Am 12.11.2020 um 00:41 schrieb David Michael :
> >> On Wed, Nov 11, 2020 at 6:20 PM Carl Eugen Hoyos
> >> wrote:
> >>> Am Mi., 11. Nov. 2020 um 16:30 Uhr schrieb David Michael
> >>> :
&g
On Wed, Nov 11, 2020 at 6:20 PM Carl Eugen Hoyos wrote:
> Am Mi., 11. Nov. 2020 um 16:30 Uhr schrieb David Michael
> :
> > There are two issues:
> >
> > The unused global integer does not make it into the compiled object
> > file, so declare it static to correct
On Wed, Nov 11, 2020 at 5:18 PM Martin Storsjö wrote:
> On Wed, 11 Nov 2020, David Michael wrote:
> > There are two issues:
> >
> > The unused global integer does not make it into the compiled object
> > file, so declare it static to correct this.
>
>
option to disable printing input offsets and delete
all newline characters to output continuous hex values to grep.
Signed-off-by: David Michael
---
configure | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure b/configure
index 2f02d7f5c8..52c02a74c8 100755
--- a/confi
On Thu, Apr 2, 2020 at 5:38 PM Michael Niedermayer
wrote:
> On Wed, Apr 01, 2020 at 12:07:55AM -0400, David Michael wrote:
> > Using a compiler with a different host triplet is considered
> > cross-compiling, even when it is for the same architecture as the
> > build syste
a cross-compiler for an
incompatible architecture will fail with -mtune=native anyway.
Signed-off-by: David Michael
---
Changes since v1:
* Use a warning instead of dropping the condition altogether
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b
On Mon, Mar 30, 2020 at 1:00 PM Derek Buitenhuis
wrote:
> On 07/03/2020 15:32, David Michael wrote:
> > Using a compiler with a different host triplet is considered
> > cross-compiling, even when it is for the same architecture as the
> > build system. With such a cross-
On Sun, Mar 22, 2020 at 11:01 PM David Michael wrote:
> On Mon, Mar 16, 2020 at 9:16 AM David Michael wrote:
> > On Sat, Mar 7, 2020 at 10:32 AM David Michael wrote:
> > > Using a compiler with a different host triplet is considered
> > > cross-compiling, e
On Mon, Mar 16, 2020 at 9:16 AM David Michael wrote:
> On Sat, Mar 7, 2020 at 10:32 AM David Michael wrote:
> > Using a compiler with a different host triplet is considered
> > cross-compiling, even when it is for the same architecture as the
> > build system. With such a
On Sat, Mar 7, 2020 at 10:32 AM David Michael wrote:
> Using a compiler with a different host triplet is considered
> cross-compiling, even when it is for the same architecture as the
> build system. With such a cross-compiler, it is still valid to
> optimize builds with --cpu=hos
an incompatible architecture
will fail with -mtune=native anyway.
Signed-off-by: David Michael
---
Hi,
I am building software in a ChromeOS-style environment where the native
build system creates a cross-compiler with a different vendor string for
each supported architecture, and cross-compiled
15 matches
Mail list logo
