DOCSLIB.ORG

How To… Gcc E Make

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
How To… Gcc E Make 1 Gcc e make How to… gcc e make I passi della compilazione Sia gcc che g++ processano file di input attraverso uno o piu' dei seguenti passi: 1) preprocessing -rimozione dei commenti -interpretazioni di speciali direttive per il preprocessore denotate da "#" come: #include - include il contenuto di un determinato file, Es. #include<math.h> #define -definisce un nome simbolico o una variabile, Es. #define MAX_ARRAY_SIZE 100 2) compilation -traduzione del codice sorgente ricevuto dal preprocessore in codice assembly 3) assembly -creazione del codice oggetto 4) linking -combinazione delle funzioni definite in altri file sorgenti o definite in librerie con la funzione main() per creare il file eseguibile. 2 Gcc e make Pre-compilazione Il preprocessor e' un programma che viene attivato dal compilatore nella fase precedente alla compilazione, detta di precompilazione. Il preprocessor legge un sorgente C e produce in output un altro sorgente C, dopo avere espanso in linea le macro, incluso i file e valutato le compilazioni condizionali o eseguito altre direttive. Una direttiva inizia sempre con il carattere pound '#' eventualmente preceduto e/o seguito da spazi. I token seguenti definiscono la direttiva ed il suo comportamento. Una direttiva al preprocessor puo' comparire in qualsiasi punto del sorgente in compilazione ed il suo effetto permane fino alla fine del file. Espansione in linea delle macro Definire una macro significa associare una stringa ad un identificatore. Ogni volta che il preprocessore C incontra l'identificatore cosi' definito, esegue la sua sostituzione in linea, con la stringa ad esso associata. La definizione delle macro avviene per mezzo della direttiva #define Esempio: #define MAX 100 #define STRING_ERR "Rilevato errore !\n" Le macro possono essere definite anche in forma paramentrica; in tal caso la sostituzione dei parametri formali con quelli attuali avviene in modo testuale durante la fase di espansione della macro. Esempio: #define NUM_SCRITTORI 100 void main(){… For(int i=0;i<NUM_SCRITTORI;i++) … } Questo consente di avere costanti con un nome (per esempio NUM_SCRITTORI rappresenta il numero di processi scrittori da allocare) usate in tutto il sorgente, definite in un solo posto e aggiornate automaticamente dappertutto non appena il valore cambia. Se un parametro formale e' preceduto dal carattere pound #, il suo valore attuale e' espanso testualmente come stringa. Esempio: 3 Gcc e make #define DEBUG_OUT(expr) fprintf(stderr, #expr " = %g\n", (float)(expr)) ... DEBUG_OUT(x*y+z); /* espansione: * fprintf(stderr, "x*y+z" " = %g\n", (float)(x*y+z)) */ E' anche possibile annullare la definizione di una macro con la direttiva #undef. Di solito #undef e' impiegata per assicurarsi che una funzione sia definita come tale, piuttosto che come macro. Un altro possibile impiego di #undef e' per la gestione della compilazione condizionale. Esempio: #undef DEBUG Tipicamente sono predefinite 5 macro: __LINE__ Valore decimale del numero della linea corrente del sorgente. __FILE__ Stringa del nome del file in corso di compilazione. __DATE__ Stringa della data di compilazione (formato Mmm dd yyyy). __TIME__ Stringa dell'ora di compilazione (formato hh:mm:ss). __STDC__ Contiene il valore 1 se il compilatore e' conforme allo standard ANSI. Di solito il compilatore accetta nella linea di comando delle opzioni per definire e cancellare delle macro analogamente a quanto viene eseguito con #define e #undef. Tipicamente tali opzioni sono -Dmacro o -Dmacro=def per definire una macro e -Umacro per eliminare la definizione. Le opzioni -D e -U vengono eseguite prima di cominciare l'attivita' di preprocessing sul sorgente. Uso ed esempi Usare ifndef per stampare un messaggio di debug #define DEBUG #ifdef DEBUG Printf(“MESSAGGIO DI DEBUG”); #endif Visto che DEBUG è diverso da 0 le la linea del printf viene compilata ed aiuta nel debug del programma. Successivamente omettendo #define DEBUG 1 le linee non verranno compilate e quindi eseguite. 4 Gcc e make Inclusione di file (#include) Le definizioni ricorrenti delle macro, le dichiarazioni dei prototype di funzione e delle variabili esterne, di solito vengono scritte, una volta per tutte, in files tradizionalmente chiamati header ed aventi normalmente estensione .h. Il preprocessore C, tramite la direttiva #include, puo' ricercare il file indicato in alcune directory standard o definite al momento della compilazione ed espanderlo testualmente in sostituzione della direttiva. Considerato che nel C ogni funzione, variabile, macro deve essere definita o dichiarata prima del suo utilizzo, risulta evidente che ha senso includere gli header file all'inizio, cioe' nella testata (e da qui deriva il nome di header), del file sorgente. La direttiva #include puo' essere impiegata in due forme: #include <nomefile> #include "nomefile" Nel 1° caso il nomefile viene ricercato in un insieme di directory standard definite dall'implementazione ed in altre che sono specificate al momento della compilazione. Nel caso della versione Unix del compilatore, le directory standard di ricerca degli header potrebbero essere /usr/include, /usr/local/include, ... Nel 2° caso il nomefile viene ricercato nella directory corrente e poi, se non e' stato trovato, la ricerca continua nelle directory standard e in quelle specificate al momento della compilazione come nel 1° caso. N.B. - Nel caso che un header venga modificato, e' necessario ricompilare tutti i sorgenti che lo includono. Compilazione condizionale Il preprocessore C al verificarsi di alcune condizioni puo' includere o escludere parti del codice sorgente alla compilazione. Le direttive che indicano al preprocessore la compilazione condizionata sono riportate di seguito: #if espressione_costante_intera #ifdef identificatore #ifndef identificatore #else #elif espressione_costante_intera #endif dove #if, #ifdef, #ifndef testano la condizione. Se risulta verificata, viene incluso per la compilazione il codice dalla riga successiva alla direttiva, fino ad incontrare una delle direttive #else, #elif o #end. In particolare #if testa l'espressione_costante_intera e se risulta diversa da zero, la condizione e' considerata verificata positivamente. L'espressione_costante_intera non puo' comprendere costanti di tipo enumerativo, operatori di cast e sizeof. 5 Gcc e make #ifdef considera superata la condizione se e' definito identificatore. #ifdef identificatore equivale a #if defined (identificatore) o #if defined identificatore #ifndef considera superata la condizione se non e' definito identificatore. #ifndef identificatore equivale a #if !defined (identificatore) o #if !defined identificatore La parte di codice successiva a #else viene passata al compilatore nel caso cha la #if, #ifdef, #ifndef non sia stata soddisfatta. La direttiva #elif equivale ad #else #if tranne il fatto di non aumentare di un livello di annidamento l'intera #if. La direttiva #endif chiude la #if, #ifdef, #ifndef del corrispondente livello di annidamento. Esempio: #ifdef DEBUG fprintf(stderr, "Linea di Debug %d\n", (int)__LINE__); #endif Compilazione Come passo intermedio, gcc trasforma il vostro codice in Assembly. Per farlo deve capire cosa intendevate fare analizzando il vostro codice. Se avete commesso degli errori di sintassi ve lo dirà e la compilazione fallirà. Di solito la gente confonde questo passo con l'intero processo di compilazione. Ma c'è ancora molto lavoro da fare per gcc. Assembly as trasforma il codice Assembly in codice oggetto. Il codice oggetto non può ancora essere lanciato sulla CPU, ma ci si avvicina molto. L'opzione -c trasforma un file .c in un file oggetto con estensione .o Se lanciamo gcc -c game.c creiamo automaticamente un file che si chiama game.o Qui siamo incappati in un punto importante. Possiamo prendere un qualsiasi file .c e creare un file oggetto da esso. Come vedremo più avanti potremo combinare questi file oggetto in un eseguibile nella fase di Link. Andiamo avanti col nostro esempio. Poiché stiamo programmando un gioco di carte abbiamo definito un mazzo di carte come un deck_t, creeremo una funziona per mischiare il mazzo. Questa funzione prenderà un puntatore a un tipo deck e lo riempie con delle carte messe a caso. Tiene traccia di quali carte sono già state aggiunte con l'array 'drawn'. Questo arraydi DECKSIZE elementi ci impedisce di duplicare un valore di carta. #include <stdlib.h> #include <stdio.h> #include <time.h> #include "deck.h" static time_t seed = 0; 6 Gcc e make void shuffle(deck_t *pdeck) { /* Tiene traccia di che numeri sono stati usati */ int drawn[DECKSIZE] = {0}; int i; /* Inizializzazione da fare una volta di rand */ if(0 == seed) { seed = time(NULL); srand(seed); } for(i = 0; i < DECKSIZE; i++) { int value = -1; do { value = rand() % DECKSIZE; } while(drawn[value] != 0); /* segna il valore come usato */ drawn[value] = 1; /* codice di debug */ printf("%i\n", value); pdeck->card[i] = value; } pdeck->dealt = 0; return; } Salvate questo file come shuffle.c. Abbiamo inserito del codice di debug in questo codice in modo che, quando viene lanciato, scriva i valori delle carte che genera. Questo non aggiunge niente alle funzionalità del programma, ma è cruciale adesso che non possiamo vedere cosa succede. Visto che stiamo appena cominciando il nostro gioco non abbiamo altro modo di sapere se la nostra funzione fa quello che vogliamo. Con il comando printf potete vedere esattamente cosa sta succedendo in modo che quando passeremo alla prossima fase sapremo che il mazzo viene mescolato bene. Dopo che saremmo soddisfatti del buon funzionamento
Load more

Recommended publications
  • Communications of the Acm
    COMMUNICATIONS CACM.ACM.ORG OF THEACM 11/2014 VOL.57 NO.11 Scene Understanding by Labeling Pixels Evolution of the Product Manager The Data on Diversity On Facebook, Most Ties Are Weak Keeping Online Reviews Honest Association for Computing Machinery tvx-full-page.pdf-newest.pdf 1 11/10/2013 12:03 3-5 JUNE, 2015 BRUSSELS, BELGIUM Course and Workshop C proposals by M 15 November 2014 Y CM Paper Submissions by MY 12 January 2015 CY CMY K Work in Progress, Demos, DC, & Industrial Submissions by 2 March 2015 Welcoming Submissions on Content Production Systems & Infrastructures Devices & Interaction Techniques Experience Design & Evaluation Media Studies Data Science & Recommendations Business Models & Marketing Innovative Concepts & Media Art TVX2015.COM [email protected] ACM Books M MORGAN& CLAYPOOL &C PUBLISHERS Publish your next book in the ACM Digital Library ACM Books is a new series of advanced level books for the computer science community, published by ACM in collaboration with Morgan & Claypool Publishers. I’m pleased that ACM Books is directed by a volunteer organization headed by a dynamic, informed, energetic, visionary Editor-in-Chief (Tamer Özsu), working closely with a forward-looking publisher (Morgan and Claypool). —Richard Snodgrass, University of Arizona books.acm.org ACM Books ◆ will include books from across the entire spectrum of computer science subject matter and will appeal to computing practitioners, researchers, educators, and students. ◆ will publish graduate level texts; research monographs/overviews of established and emerging fields; practitioner-level professional books; and books devoted to the history and social impact of computing. ◆ will be quickly and attractively published as ebooks and print volumes at affordable prices, and widely distributed in both print and digital formats through booksellers and to libraries and individual ACM members via the ACM Digital Library platform.
    [Show full text]
  • The Strange Birth and Long Life of Unix - IEEE Spectrum Page 1 of 6
    The Strange Birth and Long Life of Unix - IEEE Spectrum Page 1 of 6 COMPUTING / SOFTWARE FEATURE The Strange Birth and Long Life of Unix The classic operating system turns 40, and its progeny abound By WARREN TOOMEY / DECEMBER 2011 They say that when one door closes on you, another opens. People generally offer this bit of wisdom just to lend some solace after a misfortune. But sometimes it's actually true. It certainly was for Ken Thompson and the late Dennis Ritchie, two of the greats of 20th-century information technology, when they created the Unix operating system, now considered one of the most inspiring and influential pieces of software ever written. A door had slammed shut for Thompson and Ritchie in March of 1969, when their employer, the American Telephone & Telegraph Co., withdrew from a collaborative project with the Photo: Alcatel-Lucent Massachusetts Institute of KEY FIGURES: Ken Thompson [seated] types as Dennis Ritchie looks on in 1972, shortly Technology and General Electric after they and their Bell Labs colleagues invented Unix. to create an interactive time- sharing system called Multics, which stood for "Multiplexed Information and Computing Service." Time-sharing, a technique that lets multiple people use a single computer simultaneously, had been invented only a decade earlier. Multics was to combine time-sharing with other technological advances of the era, allowing users to phone a computer from remote terminals and then read e -mail, edit documents, run calculations, and so forth. It was to be a great leap forward from the way computers were mostly being used, with people tediously preparing and submitting batch jobs on punch cards to be run one by one.
    [Show full text]
  • The Strange Birth and Long Life of Unix - IEEE Spectrum
    The Strange Birth and Long Life of Unix - IEEE Spectrum http://spectrum.ieee.org/computing/software/the-strange-birth-and-long-li... COMPUTING / SOFTWARE FEATURE The Strange Birth and Long Life of Unix The classic operating system turns 40, and its progeny abound By WARREN TOOMEY / DECEMBER 2011 They say that when one door closes on you, another opens. People generally offer this bit of wisdom just to lend some solace after a misfortune. But sometimes it's actually true. It certainly was for Ken Thompson and the late Dennis Ritchie, two of the greats of 20th-century information technology, when they created the Unix operating system, now considered one of the most inspiring and influential pieces of software ever written. A door had slammed shut for Thompson and Ritchie in March of 1969, when their employer, the American Telephone & Telegraph Co., withdrew from a collaborative project with the Photo: Alcatel-Lucent Massachusetts Institute of KEY FIGURES: Ken Thompson [seated] types as Dennis Ritchie looks on in 1972, shortly Technology and General Electric after they and their Bell Labs colleagues invented Unix. to create an interactive time-sharing system called Multics, which stood for "Multiplexed Information and Computing Service." Time-sharing, a technique that lets multiple people use a single computer simultaneously, had been invented only a decade earlier. Multics was to combine time-sharing with other technological advances of the era, allowing users to phone a computer from remote terminals and then read e-mail, edit documents, run calculations, and so forth. It was to be a great leap forward from the way computers were mostly being used, with people tediously preparing and submitting batch jobs on punch cards to be run one by one.
    [Show full text]
  • Lecture 10: File Systems File Systems, Databases, Cloud Storage
    Lecture 10: File systems File systems, databases, cloud storage • file: a sequence of bytes stored on a computer – content is arbitrary (just bytes); any structure is imposed by the creator of the file, not by the operating system • file system: software that provides hierarchical storage and organization of files, usually on a single computer (or nearby) – a significant part of the operating system • database: an integrated collection of logically related records – data is organized and structured for efficient systematic access – may be distributed across lots of machines & geographically dispersed • database system: software that provides efficient access to information in a database – not usually part of the operating system • cloud storage: the same thing, but on someone else's computer(s) File systems: managing stored information • logical structure: users and programs see a hierarchy of folders (or directories) and files – a folder contains references to folder and files – "root" folder ultimately leads to all others – a file is just a sequence of bytes contents determined and interpreted by programs, not the operating system – a folder is a special file that contains names of other folders & files plus other information like size, time of change, etc. contents are completely controlled by the operating system • physical structure: disk drives operate in tracks, sectors, etc. – other storage devices have other physical properties • the operating system converts between these two views – does whatever is necessary to maintain the file/folder
    [Show full text]
  • Unix and Shell Programming
    UNIX AND SHELL PROGRAMMING OBJECTIVE: UNIX – Born in the dark and somber portals of Bell Labs, it was a dream that one man nurtured and cherished. Like a parent, he reared the infant with compassion and zeal. And as the fledgling grew and spread its wings, it caught the attention of the world. This chapter will explore through the basics of UNIX, along with certain commands which itself are categorized accordingly. The File System and Some File Handling Commands: The file system is one of the its simplest and it lets users not to access files not belonging to them, You will be learning about categorization of files, the significance of HOME directory, mkdir, rmdir, and absolute, relative path name. Kenneth T. Moras 8/21/2007 BRIEF HISTORY 1966 The Multiplexed Time Sharing and Computing System or MULTICS project was a joint attempt by General Electric (GE), AT&T Bell Labs and the Massachusetts Institute of Technology (MIT) at developing a stable multiuser operating system The aim is to create an operating system that could support a lot of simultaneous users (thousands!). Multics stands for Multiplexed Information and Computer service. Left Ken Thompson, Right Dennis Ritchie The people involved in the project at this time are Ken Thompson, Dennis Ritchie, Joseph Ossanna, Stuart Feldman, Doug McIIroy and Bob Morris. Although a very simple version of MULTICS could now run on a GE645 computer, it could only support 3 people and therefore the original goals of this operating system had not been met, the research and development is just so expensive and Bell Labs withdraws their sponsorship.
    [Show full text]
  • Enterprise Computing
    Computing at Extreme Scale – The Challenge and Excitement of Modern Computing Stuart Feldman Unicamp, VP, Engineering Campinas, Brasil Google 11 August 2008 1 Outline Future of Computers Expanding Frontiers of Computer Science Demands of modern online information systems: search and ads Google’s unique approaches to infrastructure: hardware, software, middleware Successes and Problems The Future – Concerns and Opportunities 2 Who Am I Vice President-Engineering for Google’s “East Coast” engineering offices • includes Canada, Brazil, Chicago, Texas Also, Past President of the ACM On a number of boards and committees • US National Science Foundation (2) • Business Schools • Australia’s NICTA Past • PhD in theory of galaxies • Early member of the “Unix bunch” at Bell Labs • Wrote Make, first Fortran 77 compiler, etc. • Went to Bellcore Research – software engineering and a detour to large-scale development • Went to IBM Research – Internet, E-commerce, long-term computer science research. 3 Future of Computers 4 Scale Measures Number of users Amount of Data • Ever • Stored • Recent • New • Simultaneous • Changed Amount of Networking and Amount of computing Communication • Total operations • Messages per second • Operations per byte of data • Bytes per second • Bytes of data analyzed per second • Kilometer-bytes per second 5 Processors Hardware progress has driven field forever • Range of possibility relevant to topics, details, constraints Current state • Stuck on practical thread speed • Able to execute lots of independent threads- multicore and massive multicore • Wirth’s Law as well as Moore’s • Specialized hardware possibility 6 Other Hardware Other relevant changes • Interconnect • Network • Memory • Storage hierarchy 7 Challenges Long term bets • Quantum computing • Molecular, etc.
    [Show full text]
  • Trusting Our Electronic Assistants
    From the Editor-in-Chief . Trusting Our Electronic Assistants BEING INTERACTIVE Munindar P. Singh • [email protected] With the rapid deployment of the Elements of Trust Internet, we now routinely interact Trust goes beyond security in that it with strangers—at both personal and concerns managing interactions at the corporate levels—and increasingly with application level. Security is about the strangers’ electronic minions. It is authenticating another party and not uncommon to buy goods—even authorizing its actions. Trust is about mundane items such as groceries— the given party’s acting in our best online. Innovations in computing pro- interest and choosing the right actions vide tools that can help us as we inter- from among those authorized. act with others. For example, programs We sometimes see trust as the can reside not only on our desktops belief that all parties will comply with but also in smart phones, PDAs, and even refrigera- legal contracts. Obviously, contracts are important tors, to help with our shopping (http://www.usato- in maintaining social order and stability; however, day.com/life/cyber/tech/review/ctd560.htm). These being trustworthy entails quite a bit more. Many programs serve end users while also meeting certain activities are performed without an explicit con- business needs, such as supply chain management. tract, so trust involves other important elements. All interacting parties face dynamically changing To begin with, trustworthiness is having the right situations. Let’s say you need unusual groceries for a capabilities. Nobody likes to trust someone who is special recipe, but the grocery store is out of those incompetent or simply unaware of important material particular ingredients.
    [Show full text]
  • National Science Foundation Advisory Committee for Cyberinfrastructure Task Force on Software for Science and Engineering Final Report, March 2011
    National Science Foundation Advisory Committee for CyberInfrastructure Task Force on Software for Science and Engineering Final Report, March 2011 Task Force Co-Chairs from the ACCI David Keyes, KAUST and Columbia Valerie Taylor, TAMU ACCI Members Tony Hey, Microsoft Stuart Feldman, Google Community Panelists Gabrielle Allen, LSU Phillip Colella, LBNL Peter Cummings, Vanderbilt Frederica Darema, AFOSR Jack Dongarra, UT Thom Dunning, UIUC Mark Ellisman, UCSD Ian Foster, ANL and UofC William Gropp, UIUC Chris Johnson, Utah Chandrika Kamath, LLNL Ravi Madduri, ANL Michael Mascagni, FSU Steve Parker, NVIDIA Padma Raghavan, PennState Anne Trefethen, Oxford Scott Valcourt, UNH Principal NSF Liaison Abani Patra, SUNY Buffalo NSF Liaisons Fahmida Choudhury, SBE, Clark Cooper, ENG, Peter McCartney, BIO, Manish Parashar, OCI, Tom Russell, OIA Barry Schneider, OCI, Jen Schopf, OCI, Nigel Sharp, MPS Although this report was prepared by a task force commissioned by the National Science Foundation, all opinions, findings, and recommendations expressed within it are those of the task force and do not necessarily reflect the views of the National Science Foundation. Preface The Software for Science and Engineering (SSE) Task Force commenced in June 2009 with a charge that consisted of the following three elements: Identify specific needs and opportunities across the spectrum of scientific software infrastructure. Characterize the specific needs and analyze technical gaps and opportunities for NSF to meet those needs through individual and systemic approaches. Design responsive approaches. Develop initiatives and programs led (or co-led) by NSF to grow, develop, and sustain the software infrastructure needed to support NSF’s mission of transformative research and innovation leading to scientific leadership and technological competitiveness.
    [Show full text]
  • What's the Greatest Software Ever Written? Page 1 of 13
    What's The Greatest Software Ever Written? Page 1 of 13 What's The Greatest Software Ever Written? Witness the definitive, irrefutable, immutable ranking of the most brilliant software programs ever hacked. By Charles Babcock, InformationWeek Aug. 14, 2006 URL: http://www.informationweek.com/story/showArticle.jhtml? articleID=191901844 Most red-blooded technologists will offer a quick opinion on what's the greatest software ever, but when you take the time to evaluate what makes software truly brilliant, the choices aren't so obvious. One of the most significant pieces of programming I know wasn't even software. Before the British built the Colossus machine, which translated German teletype code during World War II, it took the Allies up to six hours to decode a message and a day or more to pore over intelligence, draw conclusions, and pass along information to military command. After Colossus, the Allies gained a picture of German military activity across the English Channel as the day unfolded--intelligence that gave Gen. Dwight Eisenhower the confidence to launch the D-Day invasion. Colossus was built in 1944 to perform Boolean operations on a paper data tape that streamed through the machine at 30 miles an hour. Its logic was literally wired into the machine. It is, perhaps, the greatest software that never got written. So where does that leave us? First, let's set criteria for http://www.informationweek.com/shared/printableArticleSrc.jhtml?articleID=191901844 8/14/2006 What's The Greatest Software Ever Written? Page 2 of 13 what makes software great. Superior programming can be judged only within its historical context.
    [Show full text]
  • Portability - a No Longer Solved Problem Stuart Feldman Bellcore W
    CONTROVERSY Portability - A No Longer Solved Problem Stuart Feldman Bellcore W. Morven Gentleman National Research Council of Canada ABSTRACT: Of Man's First Disobedience, .. or Not long ago, the problem of software portability seemed on the way to solution. Now, the need and demand for portability is enormously greater, but solution seems much further away. Reasons include stricter requirements for portability, different expec- tations by and of the people doing the work, and a far wider range of environments in which software must function. This paper describes how this came about and modern approaches to the problem. 1. The Innocents Abroad Program portability is an old goal. There have been many notable successes, but there has been a major shift in expectations and satisfaction in the past decade. The flrst efforts were in the areas of mathematical and systems software, and a great deal of l. All the section headings refer to actual works; no prize is offered to those who identify them. -PHS @ Computing Systems, Vol. 3 'No. 2 ' Spring 1990 359 research led to good practical solutions involving clever software and concentrated activity. Thus, we find ourselves in the para- doxical situation of having better techniques and knowledge but in more trouble and with more grumpy customers. We contend that almost any program can be made portable, usually at acceptable production cost and execution effectiveness. There are many impressive examples. Even embedded systems with exotic peripherals and real-time constraints, have been suc- cessfully ported. However, the scale and scope of the problem have increased dramatically, and techniques need to be extended and upgraded to meet current demands.
    [Show full text]
  • Scrum Essentials Cards 83 the Popular Agile Framework Scrum Can Improve the Way a Development Team Works Together
    Volume 18 | Issue 3 May-June 2020 The Life of a scrum Data Byte essentials Data on the cards Outside vs. Data on the Inside The History, Status and Future of FPGAs ::::: Complete table of contents on the following two pages Features contents Data on the The History, Outside vs. Data Status, and Future MAY-JUNE on the Inside 43 of FPGAs 71 Services are essential to From the early days of building large applications telecom, through the today. Each service high-performance 2020 has its own data, and computing and data that data may reside centers of today, field- inside or outside of that programmable gate service. Where it resides arrays have been hitting determines how that data a nerve in the ASIC should be treated. community. PAT HELLAND OSKAR MENCER ET AL. Scrum Essentials Cards 83 The popular agile framework Scrum can improve the way a development team works together. Here we present a set of cards based on the Essence standard, which can make Scrum more effective. JEFF SUTHERLAND IVAR JACOBSON Volume 18 Issue 3 BRIAN KERR 2 acmqueue | may-june 2020 2 columns / departments I COMMIT TO MEMORY The Life of a Data Byte 5 As we all know, the state- of-the-art in storage media has come a ridiculously long way, from paper tape to flash. And it’s still evolving to ever faster, smaller storage technology. JESSIE FRAZELLE I contents EVERYTHING SYSADMIN Five Nonobvious Remote Work Techniques 29 If ever there were a time to refine the practice of working remotely, it is now.
    [Show full text]
  • Axiom Bibliography 1
    The 30 Year Horizon Manuel Bronstein W illiam Burge T imothy Daly James Davenport Michael Dewar Martin Dunstan Albrecht F ortenbacher P atrizia Gianni Johannes Grabmeier Jocelyn Guidry Richard Jenks Larry Lambe Michael Monagan Scott Morrison W illiam Sit Jonathan Steinbach Robert Sutor Barry T rager Stephen W att Jim W en Clifton W illiamson Volume Bibliography: Axiom Literature Citations i Portions Copyright (c) 2005 Timothy Daly The Blue Bayou image Copyright (c) 2004 Jocelyn Guidry Portions Copyright (c) 2004 Martin Dunstan Portions Copyright (c) 2007 Alfredo Portes Portions Copyright (c) 2007 Arthur Ralfs Portions Copyright (c) 2005 Timothy Daly Portions Copyright (c) 1991-2002, The Numerical ALgorithms Group Ltd. All rights reserved. This book and the Axiom software is licensed as follows: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of The Numerical ALgorithms Group Ltd. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
    [Show full text]