Skip to contentSkip to conversation

toolchain/external: fix wrapper by not passing conflicting flags

PATCH New Yann E. MORIN 2 participants 4 messages Jan 6, 2014

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 toolchain/external: fix wrapper by not passing conflicting flags

From: "Yann E. MORIN" <[email protected]>

In our wrapper, we forcibly add the -march=, -mcpu= and-mtune= flags to the actual copmpiler, this in an attempt to always generate correct and optimised code for the target.

But in some cases, the caller knows better than we do, and passes its own set, or subset of those flags. In this case, some may conflict with the ones we pass. The most prominent offender being the Linux kernel.

For example, on the ARM Rapsberry Pi, the Linux kernel will set the -march=armv6 flag and no -mcpu= flag, but we pass -mcpu=arm1176jzf-s, which conflicts:

drivers/scsi/scsi_trace.c:1:0: warning: switch -mcpu=arm1176jzf-s conflicts with -march=armv6 switch

(and so for all the files the kernel compiles, pretty messy) (note: arm1176jzf-s is not an armv6, it is an armv6zk. Yeah...)

To avoid this situation, we scan our commandline for any occurence of the possibly conflicting flags. If none is found, then we add our owns. If any is found, then we don't add any of our owns.

The idea behind this is that we trust the caller to know better than we do what it is doing. Since the biggest, and sole so far, offender is the Linux kernel, then this is a rather safe bet.

Cc Thomas Petazzoni <[email protected]>
Cc Peter Korsgaard <[email protected]>
Cc Arnout Vandecappelle <[email protected]>
---
 .../toolchain-external/ext-toolchain-wrapper.c     | 41 ++++++++++++++++------
 1 file changed, 31 insertions(+), 10 deletions(-)
toolchain/toolchain-external/ext-toolchain-wrapper.c +31 -10
index d54f1f5..dd84a5d 100644
@@ -30,21 +30,17 @@ static char sysroot[PATH_MAX];
  * that we only pass the predefined one to the real compiler if the inverse
  * option isn't in the argument list.
  * This specifies the worst case number of extra arguments we might pass
+ * Currently, we have:
+ * 	-mfloat-abi=
+ * 	-march=
+ * 	-mtune=
+ * 	-mcpu=
  */
-#define EXCLUSIVE_ARGS	1
+#define EXCLUSIVE_ARGS	4
 
 static char *predef_args[] = {
 	path,
 	"--sysroot", sysroot,
-#ifdef BR_ARCH
-	"-march=" BR_ARCH,
-#endif /* BR_ARCH */
-#ifdef BR_TUNE
-	"-mtune=" BR_TUNE,
-#endif /* BR_TUNE */
-#ifdef BR_CPU
-	"-mcpu=" BR_CPU,
-#endif
 #ifdef BR_ABI
 	"-mabi=" BR_ABI,
 #endif
@@ -157,6 +153,31 @@ int main(int argc, char **argv)
 		*cur++ = "-mfloat-abi=" BR_FLOAT_ABI;
 #endif
 
+#if defined(BR2_ARCH) || \
+    defined(BR2_TUNE) || \
+    defined(BR2_CPU)
+	/* Add our -march/cpu/tune/abi flags, but only if none are
+	 * already specified on the commandline
+	 */
+	for (i = 1; i < argc; i++) {
+		if (!strncmp(argv[i], "-march=", strlen("-march=")) ||
+		    !strncmp(argv[i], "-mtune=", strlen("-mtune=")) ||
+		    !strncmp(argv[i], "-mcpu=",  strlen("-mcpu=" )))
+			break;
+	}
+	if (i == argc) {
+#ifdef BR_ARCH
+		*cur++ = "-march=" BR_ARCH;
+#endif
+#ifdef BR_TUNE
+		*cur++ = "-mtune=" BR_TUNE;
+#endif
+#ifdef BR_CPU
+		*cur++ = "-mcpu=" BR_CPU;
+#endif
+	}
+#endif /* ARCH || TUNE || CPU */
+
 	/* append forward args */
 	memcpy(cur, &argv[1], sizeof(char *) * (argc - 1));
 	cur += argc - 1;
Signature · 1 line
1.8.1.2
#1 lore raw

PATCH 1/1 toolchain/external: fix wrapper by not passing conflicting flags

Hi all,

Quoted 69 lines · Yann E. MORIN

From: "Yann E. MORIN" <[email protected]>

In our wrapper, we forcibly add the -march=, -mcpu= and-mtune= flags to the actual copmpiler, this in an attempt to always generate correct and optimised code for the target.

But in some cases, the caller knows better than we do, and passes its own set, or subset of those flags. In this case, some may conflict with the ones we pass. The most prominent offender being the Linux kernel.

For example, on the ARM Rapsberry Pi, the Linux kernel will set the -march=armv6 flag and no -mcpu= flag, but we pass -mcpu=arm1176jzf-s, which conflicts:

drivers/scsi/scsi_trace.c:1:0: warning: switch -mcpu=arm1176jzf-s conflicts with -march=armv6 switch

(and so for all the files the kernel compiles, pretty messy) (note: arm1176jzf-s is not an armv6, it is an armv6zk. Yeah...)

To avoid this situation, we scan our commandline for any occurence of the possibly conflicting flags. If none is found, then we add our owns. If any is found, then we don't add any of our owns.

The idea behind this is that we trust the caller to know better than we do what it is doing. Since the biggest, and sole so far, offender is the Linux kernel, then this is a rather safe bet.

Cc Thomas Petazzoni <[email protected]>
Cc Peter Korsgaard <[email protected]>
Cc Arnout Vandecappelle <[email protected]>
---
 .../toolchain-external/ext-toolchain-wrapper.c     | 41 ++++++++++++++++------
 1 file changed, 31 insertions(+), 10 deletions(-)
toolchain/toolchain-external/ext-toolchain-wrapper.c +6 -10
index d54f1f5..dd84a5d 100644
@@ -30,21 +30,17 @@ static char sysroot[PATH_MAX];
  * that we only pass the predefined one to the real compiler if the inverse
  * option isn't in the argument list.
  * This specifies the worst case number of extra arguments we might pass
+ * Currently, we have:
+ *     -mfloat-abi=
+ *     -march=
+ *     -mtune=
+ *     -mcpu=
  */
-#define EXCLUSIVE_ARGS 1
+#define EXCLUSIVE_ARGS 4
 
 static char *predef_args[] = {
        path,
        "--sysroot", sysroot,
-#ifdef BR_ARCH
-       "-march=" BR_ARCH,
-#endif /* BR_ARCH */
-#ifdef BR_TUNE
-       "-mtune=" BR_TUNE,
-#endif /* BR_TUNE */
-#ifdef BR_CPU
-       "-mcpu=" BR_CPU,
-#endif
 #ifdef BR_ABI
        "-mabi=" BR_ABI,
 #endif

toolchain/toolchain-external/ext-toolchain-wrapper.c int main(int argc, char **argv) · line 158

Quoted 6 lines
toolchain/toolchain-external/ext-toolchain-wrapper.c +3 -0
@@ -157,6 +153,31 @@ int main(int argc, char **argv)
                *cur++ = "-mfloat-abi=" BR_FLOAT_ABI;
 #endif
 
+#if defined(BR2_ARCH) || \
+    defined(BR2_TUNE) || \
+    defined(BR2_CPU)

Shouldn't this be BR_* ?

Quoted 28 lines
toolchain/toolchain-external/ext-toolchain-wrapper.c +22 -1
+       /* Add our -march/cpu/tune/abi flags, but only if none are
+        * already specified on the commandline
+        */
+       for (i = 1; i < argc; i++) {
+               if (!strncmp(argv[i], "-march=", strlen("-march=")) ||
+                   !strncmp(argv[i], "-mtune=", strlen("-mtune=")) ||
+                   !strncmp(argv[i], "-mcpu=",  strlen("-mcpu=" )))
+                       break;
+       }
+       if (i == argc) {
+#ifdef BR_ARCH
+               *cur++ = "-march=" BR_ARCH;
+#endif
+#ifdef BR_TUNE
+               *cur++ = "-mtune=" BR_TUNE;
+#endif
+#ifdef BR_CPU
+               *cur++ = "-mcpu=" BR_CPU;
+#endif
+       }
+#endif /* ARCH || TUNE || CPU */
+
        /* append forward args */
        memcpy(cur, &argv[1], sizeof(char *) * (argc - 1));
        cur += argc - 1;
--

1.8.1.2

Quoted 4 lines

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

After modifying to use BR instead of BR2 variable, your patch did what was intended.
It suppressed all theses pesky messages while building the kernel.

I am currently doing a full build, will report once it's done.

#2 lore raw

PATCH 1/1 toolchain/external: fix wrapper by not passing conflicting flags

On 2014-01-06 17:07 +0100, Maxime Hadjinlian spake thusly:

Quoted 5 lines · Yann E. MORIN
Quoted 4 lines

From: "Yann E. MORIN" <[email protected]>
In our wrapper, we forcibly add the -march=, -mcpu= and-mtune= flags to the actual copmpiler, this in an attempt to always generate correct and optimised code for the target.

[--SNIP--]

Quoted 8 lines

toolchain/toolchain-external/ext-toolchain-wrapper.c int main(int argc, char **argv) · line 158

Quoted 7 lines
toolchain/toolchain-external/ext-toolchain-wrapper.c +3 -0
@@ -157,6 +153,31 @@ int main(int argc, char **argv)
                *cur++ = "-mfloat-abi=" BR_FLOAT_ABI;
 #endif
 
+#if defined(BR2_ARCH) || \
+    defined(BR2_TUNE) || \
+    defined(BR2_CPU)

Shouldn't this be BR_* ?

Doh, yes indeed. Good catch. :-)

Quoted 5 lines

After modifying to use BR instead of BR2 variable, your patch did what was intended.
It suppressed all theses pesky messages while building the kernel.

I am currently doing a full build, will report once it's done.

Thank you! :-)

Regards,
Yann E. MORIN.

Signature · 6 lines
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
#3 lore raw

PATCH 1/1 toolchain/external: fix wrapper by not passing conflicting flags

It did build without any warnings in Linux, so far so good :).

Quoted 36 lines · Yann E. MORIN

On 2014-01-06 17:07 +0100, Maxime Hadjinlian spake thusly:

Quoted 5 lines · Yann E. MORIN
Quoted 4 lines

From: "Yann E. MORIN" <[email protected]>
In our wrapper, we forcibly add the -march=, -mcpu= and-mtune= flags to the actual copmpiler, this in an attempt to always generate correct and optimised code for the target.

[--SNIP--]

Quoted 8 lines

toolchain/toolchain-external/ext-toolchain-wrapper.c int main(int argc, char **argv) · line 158

Quoted 7 lines
toolchain/toolchain-external/ext-toolchain-wrapper.c +3 -0
@@ -157,6 +153,31 @@ int main(int argc, char **argv)
                *cur++ = "-mfloat-abi=" BR_FLOAT_ABI;
 #endif
 
+#if defined(BR2_ARCH) || \
+    defined(BR2_TUNE) || \
+    defined(BR2_CPU)

Shouldn't this be BR_* ?

Doh, yes indeed. Good catch. :-)

Quoted 5 lines

After modifying to use BR instead of BR2 variable, your patch did what was intended.
It suppressed all theses pesky messages while building the kernel.

I am currently doing a full build, will report once it's done.

Thank you! :-)

Regards,
Yann E. MORIN.

--
.-----------------.--------------------.------------------.--------------------.

|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |

'------------------------------^-------^------------------^--------------------'