Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Linux operating system (OS), a U...  <--  <--- Return to Home Page
   Networked Database  Linux operating system (OS), a U...   [671 / 900] RSS
 From   To   Subject   Date/Time 
Message   Maurice Kinal    Free Hat   aarch64-raspi3b+-linux-gnu   December 13, 2018
 11:08 PM *  

Halo Free!

-={ '<Esc>:read !gcc -march=native -Q --help=target' starts }=-
The following options are target specific:
  -mabi=ABI                   		lp64
  -march=ARCH                 		armv8-a+crc
  -mbig-endian                		[disabled]
  -mbionic                    		[disabled]
  -mcmodel=                   		small
  -mcpu=CPU                   		
  -mfix-cortex-a53-835769     		[enabled]
  -mfix-cortex-a53-843419     		[enabled]
  -mgeneral-regs-only         		[disabled]
  -mglibc                     		[enabled]
  -mlittle-endian             		[enabled]
  -mmusl                      		[disabled]
  -momit-leaf-frame-pointer   		[enabled]
  -moverride=STRING           		
  -mpc-relative-literal-loads 		[enabled]
  -msign-return-address=      		none
  -mstrict-align              		[disabled]
  -msve-vector-bits=N         		scalable
  -mtls-dialect=              		desc
  -mtls-size=                 		24
  -mtune=CPU                  		
  -muclibc                    		[disabled]

  Known AArch64 ABIs (for use with the -mabi= option):
    ilp32 lp64

  Supported AArch64 return address signing scope (for use with
-msign-return-address= option):
    all non-leaf none

  The code model option names for -mcmodel:
    large small tiny

  The possible SVE vector lengths:
    1024 128 2048 256 512 scalable

  The possible TLS dialects:
    desc trad
-={ '<Esc>:read !gcc -march=native -Q --help=target' ends }=-

For the CPU in both -mcpu and -mtune cortex-a53 is/was being deployed.  Also
worth mentioning is that "-j 4" works EXCEPT when building cmake and for that
"-j 3" fixed the fatal issue.  Also, also, for some source, cmake for instance,
 --build=aarch64-unknown-linux-gnu is/was needs to be passed to configure in
order to successfully build.  Other than those few cases the new native
aarch64-raspi3b+-linux-gnu is more than just fine.  I just did a search for
aarch64-raspi3b+-linux-gnu and near as I can tell I am the only one using it so
 if you're looking to replicate I would advise using aarch64-unknown-linux-gnu
instead and keep -march=armv8-a+crc, and -mtune=cortex-a53 and/or
-cpu=cortex-a53 for optimizations for the raspberry pi 3b+.

La vida es buena,
Maurice

... No llores por mi tengo vi.
--- GNU bash, version 5.0.0(1)-beta2 (aarch64-raspi3b+-linux-gnu)
 * Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Linux operating system (OS), a U...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0804 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_uqlbc52nm2m5gsg93iim0i5ut3, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_uqlbc52nm2m5gsg93iim0i5ut3, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_uqlbc52nm2m5gsg93iim0i5ut3, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0